Getting ClassCast Exception in case of malformed webservice

[gandulf.k]

Hi, i'm using jbowss ws native with validation turned on to ensure the requests and responses are valid. In case of a xml-valid document the validation is working fine and I'm getting validation errors from the validator. But if i'm sending back a totally corrupt xml message, missing closing tags, etc. then i'm getting the following exception which is not very intuitive:

Caused by: javax.xml.ws.WebServiceException: java.lang.ClassCastException: org.jboss.ws.core.soap.TextImpl cannot be cast to org.jboss.ws.core.soap.SOAPElementI
mpl
 at org.jboss.ws.core.jaxws.client.ClientImpl.handleRemoteException(ClientImpl.java:404)
 at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:314)
 at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:172)
 at org.jboss.ws.core.jaxws.client.ClientProxy.invoke(ClientProxy.java:152)
 at $Proxy311.bookOrders(Unknown Source)
 at com.skidata.dta.server.co.v3_0.classic.impl.BookOrdersHelper.invoke(BookOrdersHelper.java:46)
 ... 12 more
Caused by: java.lang.ClassCastException: org.jboss.ws.core.soap.TextImpl cannot be cast to org.jboss.ws.core.soap.SOAPElementImpl
 at org.jboss.ws.core.CommonSOAPBinding.getParameterFromMessage(CommonSOAPBinding.java:894)
 at org.jboss.ws.core.CommonSOAPBinding.unbindResponseMessage(CommonSOAPBinding.java:634)
 at org.jboss.ws.core.CommonClient.invoke(CommonClient.java:380)
 at org.jboss.ws.core.jaxws.client.ClientImpl.invoke(ClientImpl.java:302)
 ... 16 more

I digged into the code a little bit and found out that the actual XML parser exception which i'd like to get is ignored because the SOAPMessageUnMarshallerHTTP is creating a MessageFactory with ignoreParseErrors = true. (line 82 in 3.1.1 source)

 MimeHeaders mimeHeaders = getMimeHeaders(metadata);
 soapMsg = getMessageFactory().createMessage(mimeHeaders, inputStream, true);

Which catches the Parse Excpetion and simply returns null in case of a parse error.

Is there another way than changing the source code to change this behaviour, because i'd like to use the original distribution and not apatched one which will be a mess to update later...

thanks gandulf

[asoldano]

The validation you turn on is a schema validation. Catching exception regarding bad xml is something different. This said, please fill in a jira about this, we might evaluate removing the ignoreParseErrors=true flag.

[gandulf.k]

ok i reported an issue for it:

https://jira.jboss.org/jira/browse/JBWS-2651

thanks gandulf[/url]

[krishnaroopa]

Hi

We are getting the same issue. As of the jira, though the priority is major, no one is assigned. When it will addressed?

For the time being, what is the work around to proceed further

[asoldano]

Scheduled for 3.2.1.

[krishnaroopa]

Though we are getting the same exception,. I have checked the response returned, the xml is valid. But could not found out why this exception occurs,.

AS you said, it is scheduled for 3.2.1, we have our deliverables by 15th. Is there any work around?

Thanks
KRS

[xalperte]

Hi Alessio,

Excuse me, we are having this problem in out JBoss AS 4.2.3GA installation, I think that we can only run the 3.1.1 version of the JBoss WS Native libraries. What we can do in order to solve this problem?

Our problem happen when we try to access a WebService using the Birt Reporting Tool (WebService Data Source), the Birt is sending the following Request xml:

<?xml version="1.0"?>

<SOAP-ENV:Envelope

xmlns:xsd="http://www.w3.org/2001/XMLSchema"

xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">

    <SOAP-ENV:Body>

        <m:findAll xmlns:m="http://client.professional.ws.bdpt.rudder.com/">

        </m:findAll>

    </SOAP-ENV:Body>

</SOAP-ENV:Envelope>

Thanks in advance

Kind regards