[
https://issues.jboss.org/browse/TEIID-2567?page=com.atlassian.jira.plugin...
]
Steven Hawkins updated TEIID-2567:
----------------------------------
Issue Type: Task (was: Bug)
Any vdb.xml changes must be backwards compatible, so we can introduce alternate handling,
but not remove the old way.
We broadly discussed vdb.xml changes early in the cycle and didn't end up pursuing
much in the way of cleanups.
The current allow-language as an element is just to follow the same pattern as the other
allows. The choice reflects that you are either setting a language permission or a crud
permission (they affect different schema objects, so there is no need to let them
overlap).
Also it doesn't really make sense to just convert it to an attribute while leaving the
other allows as elements. So it sounds like what you are advocating is just converting
all allows to attributes (possibly with shortened names) with no notion of what attribute
sets should be used together.
issues with permission element in vdb-deployer.xsd contains
problematic choice node
-----------------------------------------------------------------------------------
Key: TEIID-2567
URL:
https://issues.jboss.org/browse/TEIID-2567
Project: Teiid
Issue Type: Task
Affects Versions: 8.4
Reporter: Barry LaFond
Assignee: Steven Hawkins
Fix For: 8.4.1
Having a lot of trouble trying to tweak our JaxB VDB element classes to accommodate the
permission's choice node which contains a <sequence> and an <element>.
This structure is basically impossible to unmarshall using JAXB annotations (i.e.
@XmlElements(value= {}) )
Would clean things up to convert the <allow-language> element to an attribute:
<xs:attribute name="allow-language" type="xs:boolean"/> and
place it on the <permission> element AND remove the <choice> node entirely
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira