You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by "Tore Green (JIRA)" <xm...@xml.apache.org> on 2007/03/23 15:14:32 UTC

[jira] Created: (XMLBEANS-319) Element order broken in global complexType using

Element order broken in global complexType using <any>
------------------------------------------------------

                 Key: XMLBEANS-319
                 URL: https://issues.apache.org/jira/browse/XMLBEANS-319
             Project: XMLBeans
          Issue Type: Bug
    Affects Versions: Version 2.1, Version 2.2
         Environment: Win2k, sun jdk150_06
            Reporter: Tore Green


The attached schema cause elements to occur in the wrong order in the generated xml. Elements occur in the order the setA() and setB() methods are called rather that the order of the sequence.

This seems to occur when there is an <any> in the sequence that is in a global complextype. Using an anonymous complexType in the element gives the correct order so that might be my workaround for the moment.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[jira] Updated: (XMLBEANS-319) Element order broken in global complexType using

Posted by "Tore Green (JIRA)" <xm...@xml.apache.org>.
     [ https://issues.apache.org/jira/browse/XMLBEANS-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tore Green updated XMLBEANS-319:
--------------------------------

    Attachment: AB.xsd

Schema that illustrates the issue

> Element order broken in global complexType using <any>
> ------------------------------------------------------
>
>                 Key: XMLBEANS-319
>                 URL: https://issues.apache.org/jira/browse/XMLBEANS-319
>             Project: XMLBeans
>          Issue Type: Bug
>    Affects Versions: Version 2.1, Version 2.2
>         Environment: Win2k, sun jdk150_06
>            Reporter: Tore Green
>         Attachments: AB.xsd, AnyBug.java
>
>
> The attached schema cause elements to occur in the wrong order in the generated xml. Elements occur in the order the setA() and setB() methods are called rather that the order of the sequence.
> This seems to occur when there is an <any> in the sequence that is in a global complextype. Using an anonymous complexType in the element gives the correct order so that might be my workaround for the moment.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org


[jira] Updated: (XMLBEANS-319) Element order broken in global complexType using

Posted by "Tore Green (JIRA)" <xm...@xml.apache.org>.
     [ https://issues.apache.org/jira/browse/XMLBEANS-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Tore Green updated XMLBEANS-319:
--------------------------------

    Attachment: AnyBug.java

Attached java class that illustrates this issue

> Element order broken in global complexType using <any>
> ------------------------------------------------------
>
>                 Key: XMLBEANS-319
>                 URL: https://issues.apache.org/jira/browse/XMLBEANS-319
>             Project: XMLBeans
>          Issue Type: Bug
>    Affects Versions: Version 2.1, Version 2.2
>         Environment: Win2k, sun jdk150_06
>            Reporter: Tore Green
>         Attachments: AB.xsd, AnyBug.java
>
>
> The attached schema cause elements to occur in the wrong order in the generated xml. Elements occur in the order the setA() and setB() methods are called rather that the order of the sequence.
> This seems to occur when there is an <any> in the sequence that is in a global complextype. Using an anonymous complexType in the element gives the correct order so that might be my workaround for the moment.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org