[
https://issues.jboss.org/browse/TEIID-2729?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2729:
---------------------------------------
Warnings don't really make sense unless we are going to enforce the existing schema
again at some point. If we remain flexible or relax the schema, then the warnings would
just be clutter.
Also how strict do we want to be? Should we also reject incorrect attributes?
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
Fix For: 8.7
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 was sent by Atlassian JIRA
(v6.4.11#64026)