what is drawback in having the "allows-language" with other allows? It is just scope issue that it needs to defined at permission level?

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