You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by "Gary Tully (JIRA)" <ji...@apache.org> on 2010/04/23 13:49:25 UTC

[jira] Commented: (AMQ-2709) Refactor core XML schema to use xs:all types in place of xs:sequence

    [ https://issues.apache.org/activemq/browse/AMQ-2709?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59055#action_59055 ] 

Gary Tully commented on AMQ-2709:
---------------------------------

The order is alphabetical so it is not too hard to remember but this is fair comment.

> Refactor core XML schema to use xs:all types in place of xs:sequence
> --------------------------------------------------------------------
>
>                 Key: AMQ-2709
>                 URL: https://issues.apache.org/activemq/browse/AMQ-2709
>             Project: ActiveMQ
>          Issue Type: Improvement
>    Affects Versions: 5.3.1
>            Reporter: Fintan Bolton
>             Fix For: 5.4.0
>
>
> It is much more convenient to use xs:all instead of xs:sequence in a schema that describes a configuration file. In a configuration file, it normally does not matter what order you insert child elements inside a parent element. Having to remember the arbitrary sequence in which the elements appear in the schema is a pain!
> For example, when I went to insert a <networkConnectors> element inside a <broker> element, I was surprised to find that my XML editor complaining that this was not schema compliant. It turns out that I have to insert the <networkConnectors> element in *exactly* the right spot in order to comply with the schema.
> This change would also be backward compatible with existing XML files.

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