[
https://issues.jboss.org/browse/TEIID-2729?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2729:
---------------------------------------
Mark what you are requesting is potentially valid. The parsing logic basically supports
an "all" paradigm rather than enforcing sequences, so mostly this would be a
change to relax the schema. We would just have to make sure that clarity is not being
lost.
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