Ever since I switched to axis2-1-1 my client stubs have generated the
following exception whenever they receive a soap fault from the server.
(the stub code is generated by WSDL2java)
OSCARSStub threw exception
org.apache.axiom.om.impl.llom.OMElementImpl
java.lang.ClassCastException: org.apache.axiom.om.impl.llom.OMElementImpl
at
org.apache.axiom.soap.impl.llom.SOAPFaultImpl.getCode(SOAPFaultImpl.java:101)
at
org.apache.axis2.description.OutInAxisOperationClient.execute(OutInAxisOperation.java:312)
at net.es.oscars.service.OSCARSStub.cancelReservation(Unknown
Source)
at net.es.oscars.client.Client.cancelReservation(Unknown Source)
at CancelReservationClient.main(Unknown Source)
I have been logging the reply message to see what it really wrong and
the message looks ok to me.
DEBUG [httpclient.wire.content] << "<?xml version='1.0'
encoding='UTF-8'?><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><soapenv:Header
/><soapenv:Body><soapenv:Fault><faultcode>soapenv:Client</faultcode><faultstring>java.lang.ExceptionInInitializerError</faultstring><detail><Exception>org.apache.axis2.AxisFault:
java.lang.ExceptionInInitializerError; nested exception is: [\n]"
DEBUG [httpclient.wire.content] <<
"[0x9]java.lang.ExceptionInInitializerError[\n]"
.. long stack trace of error ...
"</Exception></detail></soapenv:Fault></soapenv:Body></soapenv:Envelope>"
Has any one else seen this? It was working ok with axis2-1.0. Did I miss
some trick in switching to the 2.1.1 release? I have just tried the Nov
29 nightly build, but it didn't help.
Mary
---------------------------------------------------------------------
Mary R. Thompson <[EMAIL PROTECTED]>
Secure Grid Technologies Group (510) 486-7408
Lawrence Berkeley National Lab http://dsd.lbl.gov/~mrt
----------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
