[
https://issues.jboss.org/browse/TEIID-2729?page=com.atlassian.jira.plugin...
]
Ramesh Reddy commented on TEIID-2729:
-------------------------------------
I do not know of a way to specify as such in schema, and that is how schema validation
works. Since the schema is already dictating that user should define the elements in
certain order, the user should follow. I know having flexibility would be good, but not
basis for any real requirement. I suggest we reject this JIRA.
Dynamic VDB xml requires sibling elements to be in a certain order
------------------------------------------------------------------
Key: TEIID-2729
URL:
https://issues.jboss.org/browse/TEIID-2729
Project: Teiid
Issue Type: Enhancement
Components: AdminApi
Affects Versions: 8.5
Reporter: Mark Drilling
Assignee: Steven Hawkins
In my *-vdb.xml, I have a model defined per following snippet:
<model name="myModel" type="PHYSICAL"
visible="true">
<source name="myModel" translator-name="hive"
connection-jndi-name="Hive12Src" />
<property name="trimColumnNames" value="true" />
</model>
The vdb.xml failed to parse, so I moved the <property> element ahead of
<source> and then it worked.
I don't think element ordering should matter in this case?
--
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