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

[Ramesh Reddy (JIRA)]

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

Ramesh Reddy commented on TEIID-2729:
-------------------------------------

IMO, validation out weighs the convenience. Granted we can remove validation, then we need to do certain tasks in code, which seems counter intuitive. 

May be  can put choice block around property, duplicate it before and after like

{code}
<xs:element name="description" type="xs:string" minOccurs="0"/>
<xs:choice minOccurs="0" maxOccurs="unbounded">
    <xs:element name="property" type="property"/>
<xs:choice>
<xs:element name="source" minOccurs="0" maxOccurs="unbounded">
<xs:choice minOccurs="0" maxOccurs="unbounded">
    <xs:element name="property" type="property"/>
<xs:choice>
{code}

Not even sure that is valid, sure does looks like a hack.


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