mule-axis.xsd causing Unique Particle Attribution violation

[knaas]

The mule-axis.xsd is showing up with the dreaded cos-nonambig error in our environment.  We are running Java1.5 with Mule2-RC2.  I have attached a stripped down config file that demonstrates the problem.  Try to bootstrap a FunctionalTestCase using this config file.

I see that there is an existing bug which demonstrates a similar problem at http://mule.mulesource.org/jira/browse/MULE-2091.  

Caused by: org.springframework.beans.factory.xml.XmlBeanDefinitionStoreException: Line 116 in XML document from class path resource [test-webservice-config.xml] is invalid; nested exception is org.xml.sax.SAXParseException: cos-nonambig: "http://www.mulesource.org/schema/mule/core/2.0":property and "http://www.mulesource.org/schema/mule/core/2.0":property (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:389)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:327)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:295)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:143)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:178)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:149)
        at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:212)
        at org.mule.config.spring.MuleApplicationContext.loadBeanDefinitions(MuleApplicationContext.java:199)
        at org.springframework.context.support.AbstractRefreshableApplicationContext.refreshBeanFactory(AbstractRefreshableApplicationContext.java:97)
        at org.springframework.context.support.AbstractApplicationContext.obtainFreshBeanFactory(AbstractApplicationContext.java:411)
        at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:338)
        at org.mule.config.spring.MuleApplicationContext.<init>(MuleApplicationContext.java:121)
        at org.mule.config.spring.MuleApplicationContext.<init>(MuleApplicationContext.java:53)
        at org.mule.config.spring.SpringXmlConfigurationBuilder.createSpringParentRegistry(SpringXmlConfigurationBuilder.java:82)
        at org.mule.config.spring.SpringXmlConfigurationBuilder.doConfigure(SpringXmlConfigurationBuilder.java:58)
        at org.mule.config.builders.AbstractConfigurationBuilder.configure(AbstractConfigurationBuilder.java:33)
        ... 24 more
Caused by: org.xml.sax.SAXParseException: cos-nonambig: "http://www.mulesource.org/schema/mule/core/2.0":property and "http://www.mulesource.org/schema/mule/core/2.0":property (or elements from their substitution group) violate "Unique Particle Attribution". During validation against this schema, ambiguity would be created for those two particles.
        at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.createSAXParseException(ErrorHandlerWrapper.java:236)
        at com.sun.org.apache.xerces.internal.util.ErrorHandlerWrapper.error(ErrorHandlerWrapper.java:172)
        at com.sun.org.apache.xerces.internal.impl.XMLErrorReporter.reportError(XMLErrorReporter.java:382)
        at com.sun.org.apache.xerces.internal.impl.xs.XSConstraints.reportSchemaError(XSConstraints.java:315)
        at com.sun.org.apache.xerces.internal.impl.xs.XSConstraints.fullSchemaChecking(XSConstraints.java:463)
        at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.handleEndElement(XMLSchemaValidator.java:2246)
        at com.sun.org.apache.xerces.internal.impl.xs.XMLSchemaValidator.endElement(XMLSchemaValidator.java:814)
        at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanEndElement(XMLNSDocumentScannerImpl.java:719)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(XMLDocumentFragmentScannerImpl.java:1685)
        at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:368)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:834)
        at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:764)
        at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:148)
        at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:250)
        at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:292)
        at org.springframework.beans.factory.xml.DefaultDocumentLoader.loadDocument(DefaultDocumentLoader.java:75)
        at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:381)
        ... 39 more


test-webservice-config.xml

[Mark Baker]

Did you ever figure out a work around for this?  I'm getting the exact same error with Mule 2.0.0 and the following config file line:

 <axis:connector name="axisConnector" serverConfig="esb-axis-server-config.wsdd"/>

[Daniel Feist]

Hi,

We don't have this issue with other schemas, so i'm guessing there  
shouldn't be a problem fixing this for axis schema.

I created this issue: http://mule.mulesource.org/jira/browse/MULE-3231

If this is causing you issues, as in stopping Mule start up, you  
should be able to turn of strict validation which should get you by  
for now until we get 2.0.1 out.  How you turn it off depends on the  
parser you are using.

Dan

On 14 Apr 2008, at 19:21, Mark Baker wrote:

>
> Did you ever figure out a work around for this?  I'm getting the  
> exact same
> error with Mule 2.0.0 and the following config file line:
>
> <axis:connector name="axisConnector"
> serverConfig="esb-axis-server-config.wsdd"/>
>
> --
> View this message in context: http://www.nabble.com/mule-axis.xsd-causing-Unique-Particle-Attribution-violation-tp15312820p16691294.html
> Sent from the Mule - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>    http://xircles.codehaus.org/manage_email
>
>

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[Andrew Perepelytsya]

My suggestion is the outdated XML parsers. Can you check what's in your endorsed Mule's folders and/or JRE's one? (need a list of libraries). Are you running standalone? Which JDK?

The problem could be that e.g. Eclipse might be using an older xml parser OOTB. This has to be done, of course, after you jump to 2.0.0 final, there were many updates to schemas in between.

Andrew

[Daniel Feist]

Andrew,

I reproduced this one, it occurs with axis schema but not others.  
These are the 2.0.0 schema's.

Dan

On 15 Apr 2008, at 09:42, Andrew Perepelytsya wrote:

> My suggestion is the outdated XML parsers. Can you check what's in  
> your endorsed Mule's folders and/or JRE's one? (need a list of  
> libraries). Are you running standalone? Which JDK?
>
> The problem could be that e.g. Eclipse might be using an older xml  
> parser OOTB. This has to be done, of course, after you jump to 2.0.0  
> final, there were many updates to schemas in between.
>
> Andrew


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email