[
https://issues.jboss.org/browse/TEIID-2567?page=com.atlassian.jira.plugin...
]
Barry LaFond commented on TEIID-2567:
-------------------------------------
From the <permission> element standpoint there is still a choice
of which resource type the permission is applied to: table/column or
"language".
So changing all allows to attributes would cloud the issue a bit if just looking at the
schema, but Designer could still handle it in our business logic.
1) If you don't foresee any more "choices" or resource types for
permissions, then I'd vote for attributes.
2) If you do think you'll add more choices, then I'd convert the <sequence>
to a named type and I'm pretty sure JAXB could handle it.
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