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

[Steven Hawkins (JIRA)]

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

Steven Hawkins commented on TEIID-2729:
---------------------------------------

> I do not care much about the placement of elements if there is a way we can do that

That's exactly what we're saying here.  The parsing logic effectively doesn't care, but would need a bit of refinement to be more strict (ensure only one of some elements, correct attributes, etc.).  The xsd does care - and there's not a simple change to relax it that I can see.

> I would rather be strict than try to interpret what those wrong attributes mean.

You mean strict in the parsing correct?



> 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)