axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Nick Gallardo (JIRA)" <>
Subject [jira] Commented: (AXIS2-2548) Handler test with fault causes exception
Date Tue, 19 Jun 2007 14:12:25 GMT


Nick Gallardo commented on AXIS2-2548:


This problem surfaced because of some of the conversions that we were having to do between
SAAJ and Axiom for the JAX-WS handler support.

When a fault is stored in a SOAP Axiom structure, it is always represented as a SOAP 1.2 fault.
 So, if I walked that and tried to build a SOAP 1.1 fault, I'd be creating elements with the
wrong QName.  For now, the solution is to serialize the whole structure and then read it back
in.  That's horribly non-performant, but at least a step to get us going.  Once I get the
patch integrated, I'll build a small sample that shows what I'm talking about and we can see
how to solve that at the Axiom level.

> Handler test with fault causes exception
> ----------------------------------------
>                 Key: AXIS2-2548
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: jaxws
>            Reporter: Mike Rheinheimer
>            Assignee: Nick Gallardo
> This is most likely an axiom problem, but opened against JAXWS until such determination
is made.  When I enable the AddNumbersHandlerTests.testAddNumbersWithFault, I get:
> java.lang.ClassCastException:
incompatible with org.apache.axiom.soap.SOAPFault
> 	at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.createSystemException(
> 	at org.apache.axis2.jaxws.marshaller.impl.alt.MethodMarshallerUtils.demarshalFaultResponse(
> 	at org.apache.axis2.jaxws.marshaller.impl.alt.DocLitWrappedPlusMethodMarshaller.demarshalFaultResponse(
> 	at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.getFaultResponse(
> 	at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.createResponse(
> 	at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invokeSEIMethod(
> 	at org.apache.axis2.jaxws.client.proxy.JAXWSProxyHandler.invoke(
> 	at $Proxy19.addNumbersHandler(Unknown Source)
> 	at org.apache.axis2.jaxws.sample.AddNumbersHandlerTests.testAddNumbersHandlerWithFault(
> 	at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> 	at sun.reflect.NativeMethodAccessorImpl.invoke(
> 	at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> 	at java.lang.reflect.Method.invoke(
> 	at junit.framework.TestCase.runTest(
> 	at junit.framework.TestCase.runBare(
> 	at junit.framework.TestResult$1.protect(
> 	at junit.framework.TestResult.runProtected(
> 	at
> 	at
> 	at junit.framework.TestSuite.runTest(
> 	at
> 	at junit.framework.TestSuite.runTest(
> 	at
> 	at junit.extensions.TestDecorator.basicRun(
> 	at junit.extensions.TestSetup$1.protect(
> 	at junit.framework.TestResult.runProtected(
> 	at
> 	at
> 	at
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(
> 	at
> 	at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.main(
> I believe Nick has worked on this code before and can address it.  If not, I'll take
a look.

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

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message