activemq-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bernhard Wellhöfer (JIRA) <j...@apache.org>
Subject [jira] Commented: (AMQ-929) Invalid XSD (according to XML Spy)
Date Tue, 29 May 2007 07:55:34 GMT

    [ https://issues.apache.org/activemq/browse/AMQ-929?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_39174
] 

Bernhard Wellhöfer commented on AMQ-929:
----------------------------------------

The new XSD works fine in my version of XMLSpy.

> Invalid XSD (according to XML Spy)
> ----------------------------------
>
>                 Key: AMQ-929
>                 URL: https://issues.apache.org/activemq/browse/AMQ-929
>             Project: ActiveMQ
>          Issue Type: Bug
>    Affects Versions: 4.1.0
>         Environment: N/A
>            Reporter: Stephen Cresswell
>            Priority: Minor
>         Attachments: activemq.xsd
>
>
> XmlSpy reports http://people.apache.org/repository/org.apache.activemq/xsds/activemq-core-4.1-incubator-SNAPSHOT.xsd
is invalid with the following message:
> <xs:element ref='tns:topic'> makes the content model non-deterministic. Possible
causes: name equality, overlapping occurance or substitution groups.
> It's complaining because it has no way to validate whether it should validate against
tns:topic/tns:queue or the xs:any for the following element
> <xs:element name='destination' minOccurs='0' maxOccurs='1'>
>    <xs:complexType>
>       <xs:choice minOccurs='0' maxOccurs='1'>
>          <xs:element ref='tns:queue'/>
>          <xs:element ref='tns:topic'/>
>          <xs:any/>
>       </xs:choice>
>    </xs:complexType>
> </xs:element>
> Possible fix adapted from http://www.thescripts.com/forum/threadedpost1605613.html:
> <xs:element name="destination" minOccurs="0" maxOccurs="1">
> 	<xs:complexType>
> 		<xs:choice minOccurs="0" maxOccurs="1">
> 			<xs:element name="extensions">
> 				<xs:sequence maxOccurs="1">
> 					<xs:any/>				
> 				</xs:sequence>
> 			</xs:element>
> 			<xs:element ref="tns:queue"/>
> 			<xs:element ref="tns:topic"/>
> 		</xs:choice>
> 	</xs:complexType>
> </xs:element>
> But I suspect difficult to fix as the XSD is autogenerated + you'll lose backwards compatability
with previous documents. The problem occurs repeatedly throughout the schema.

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


Mime
View raw message