activemq-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lionel Cons (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (APLO-235) Invalid apollo.xsd
Date Fri, 10 Aug 2012 13:44:29 GMT

    [ https://issues.apache.org/jira/browse/APLO-235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13432730#comment-13432730
] 

Lionel Cons commented on APLO-235:
----------------------------------

Unfortunately, using apache-apollo-99-trunk-20120810.034513-80-unix-distro.tar.gz (apollo.xsd
= 44888 bytes = cc7b8d278a7c3f2b01a1babcf095418d md5), I still see:

WARNING: Error during schemas loading: cos-nonambig: "http://activemq.apache.org/schema/activemq/apollo":destination_load
and "http://activemq.apache.org/schema/activemq/apollo":destination_load (or elements from
their substitution group) violate "Unique Particle Attribution". During validation against
this schema, ambiguity would be created for those two particles.

                
> Invalid apollo.xsd
> ------------------
>
>                 Key: APLO-235
>                 URL: https://issues.apache.org/jira/browse/APLO-235
>             Project: ActiveMQ Apollo
>          Issue Type: Bug
>         Environment: Apollo 1.4
>            Reporter: Lionel Cons
>            Assignee: Hiram Chirino
>             Fix For: 1.5
>
>
> With Apollo 1.3's XSD, the minimal apollo.xml file of the User Manual can be validated
without any problem.
> With Apollo 1.4's XSD on the same file I get:
> WARNING: Error during schemas loading: cos-nonambig: "http://activemq.apache.org/schema/activemq/apollo":destination_load
and "http://activemq.apache.org/schema/activemq/apollo":destination_load (or elements from
their substitution group) violate "Unique Particle Attribution". During validation against
this schema, ambiguity would be created for those two particles.
> It looks like APLO-85 is back...

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message