3 Replies Latest reply on Jan 28, 2009 1:13 AM by praveen.govardhana

JBossXBException: Failed to parse source

swamini2 Nov 11, 2006 11:09 PM

I am using JBossAS4.0.5 with JBossWS1.0.3. I have followed JBossWS user guide to developed a JSR181 based web service. I started with WSDL and generated Java interface using wstools.sh. After implementing the interface, I packaged the jaxrpc-mapping.xml, application-client.xml, jboss-client.xml, web.xml, WSDL file and compiled classes into a WAR file. The deployment went fine and JBoss 4.0.5 server starts fine. I can access my webservice using a browser. However when I access it using a Java client, I get following error:

Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Not supported xsdType: anyType, hashCode=-842881210
 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
er.java:156)
 at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java
:126)
 at org.jboss.ws.jaxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshall
erImpl.java:63)
 ... 32 more
Caused by: java.lang.IllegalStateException: Not supported xsdType: anyType, hash
Code=-842881210
 at org.jboss.xb.binding.SimpleTypeBindings.unmarshal(SimpleTypeBindings.
java:940)
 at org.jboss.xb.binding.sunday.unmarshalling.CharactersHandler.unmarshal
(CharactersHandler.java:111)
 at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHa
ndler.unmarshal(RtCharactersHandler.java:64)
 at org.jboss.xb.binding.sunday.unmarshalling.CharactersHandler.unmarshal
(CharactersHandler.java:116)
 at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHa
ndler.unmarshal(RtCharactersHandler.java:64)
 at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endEle
ment(SundayContentHandler.java:599)
> more clipboard.txt
Caused by: org.jboss.xb.binding.JBossXBException: Failed to parse source: Not su
pported xsdType: anyType, hashCode=-842881210
 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
er.java:156)
 at org.jboss.xb.binding.UnmarshallerImpl.unmarshal(UnmarshallerImpl.java
:126)
 at org.jboss.ws.jaxb.JBossXBUnmarshallerImpl.unmarshal(JBossXBUnmarshall
erImpl.java:63)
 ... 32 more
Caused by: java.lang.IllegalStateException: Not supported xsdType: anyType, hash
Code=-842881210
 at org.jboss.xb.binding.SimpleTypeBindings.unmarshal(SimpleTypeBindings.
java:940)
 at org.jboss.xb.binding.sunday.unmarshalling.CharactersHandler.unmarshal
(CharactersHandler.java:111)
 at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHa
ndler.unmarshal(RtCharactersHandler.java:64)
 at org.jboss.xb.binding.sunday.unmarshalling.CharactersHandler.unmarshal
(CharactersHandler.java:116)
 at org.jboss.xb.binding.sunday.unmarshalling.impl.runtime.RtCharactersHa
ndler.unmarshal(RtCharactersHandler.java:64)
 at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endEle
ment(SundayContentHandler.java:599)
 at org.jboss.xb.binding.sunday.unmarshalling.SundayContentHandler.endEle
ment(SundayContentHandler.java:133)
 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser$DelegatingContentHan
dler.endElement(SaxJBossXBParser.java:273)
 at org.apache.xerces.parsers.AbstractSAXParser.endElement(Unknown Source
)
 at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanEndElement(Unknow
n Source)
 at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContent
Dispatcher.dispatch(Unknown Source)
 at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Un
known Source)
 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
 at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
 at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
 at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source)
 at org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser.parse(Unknown Sour
ce)
 at org.jboss.xb.binding.parser.sax.SaxJBossXBParser.parse(SaxJBossXBPars
er.java:152)
 ... 34 more

It looks like some schema has xsd:anyType in it. However neither WSDL nor any imported schema has anyType in it.

Please help understand why this error is coming.

1. Re: JBossXBException: Failed to parse source

thomas.diesler Nov 16, 2006 5:15 AM (in response to swamini2)

If this still shows with 1.0.4, please create a jira issue and attach a sample deployment + source to it.
Actions

2. Re: JBossXBException: Failed to parse source

electren Apr 19, 2007 7:42 AM (in response to swamini2)

I use 1.0.4 and have this problem also...

I there a solution already??

Can't find some Jira-Tasks...

My exception:

Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: org.jboss.ws.binding.BindingException: org.jboss.ws.jaxb.UnmarshalException: Failed to parse source: Requested element anmeldenamen is not allowed in this position in the sequence. The next element should be {http://cow.service.app.fm.business.de}anmeldenamen
 at com.sun.xml.ws.encoding.soap.ClientEncoderDecoder.toMessageInfo(ClientEncoderDecoder.java:84)
 at com.sun.xml.ws.encoding.soap.client.SOAPXMLDecoder.toMessageInfo(SOAPXMLDecoder.java:209)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.receive(SOAPMessageDispatcher.java:538)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.doSend(SOAPMessageDispatcher.java:258)
 at com.sun.xml.ws.protocol.soap.client.SOAPMessageDispatcher.send(SOAPMessageDispatcher.java:137)
 at com.sun.xml.ws.encoding.soap.internal.DelegateBase.send(DelegateBase.java:84)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.implementSEIMethod(EndpointIFInvocationHandler.java:172)
 at com.sun.xml.ws.client.EndpointIFInvocationHandler.invoke(EndpointIFInvocationHandler.java:106)
 at $Proxy8.pruefeLogin(Unknown Source)
 at main.java.WsLogin.main(WsLogin.java:68)

3. Re: JBossXBException: Failed to parse source

praveen.govardhana Jan 28, 2009 1:13 AM (in response to swamini2)

JBossXBException: Failed to parse source
Actions

Go to original post