[teiid-issues] [JBoss JIRA] (TEIID-2729) Dynamic VDB xml requires sibling elements to be in a certain order

[Mark Drilling (JIRA)]

    [ https://issues.jboss.org/browse/TEIID-2729?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12921879#comment-12921879 ] 

Mark Drilling commented on TEIID-2729:
--------------------------------------

There are ways to specify in schema - http://stackoverflow.com/questions/3971799/xml-schema-order-of-elements

Again, I am not saying it's possible for this case but couldn't you look into it.  IMO there should not be an ordering restriction.  The 'real requirement' would be to help prevent a user from creating a seemingly valid vdb.xml and have it fail.  
                
> 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