Axis2 integration - allow users to deploy jax-ws test, log the exceptions, set
a few more messagecontext properties
-------------------------------------------------------------------------------------------------------------------
Key: GERONIMO-2802
URL: https://issues.apache.org/jira/browse/GERONIMO-2802
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: webservices
Environment: winxp + sun 1.5 jdk
Reporter: Lin Sun
Fix For: 2.0
This patch contains the following updates to current axis2 integration code:
1) removed a few unnecessary imports
2) had to comment out a line where we setEndInterface to webserviceAnnot, as
this is causing an axis2 validation error upon the war deployment. With this
change, I was able to run .wsdl request.
3) the code didn't set setAxisService on the messagecontext inside of
doservice2(). This caused a "The requested service could not be found" error
from axis2 when processing post request .
4) also set a few other messagecontext properties and added the
Axis2RequestResponseTransport inner class that can allow for an acknowledgement
to be transmitted before processing has completed and also allow for processing
to be paused and resumed on a separate thread without having a response be sent
back.
5) also tried to log the exceptions when statuscode=500 during doservice calls.
The most recent error is:
org.apache.axis2.AxisFault: javax.xml.bind.UnmarshalException
- with linked exception:
[javax.xml.bind.UnmarshalException: unexpected element (uri:"http://hello_world_
soap_http.apache.org", local:"greetMe"). Expected elements are (none)]; nested e
xception is:
javax.xml.ws.WebServiceException: javax.xml.bind.UnmarshalException
- with linked exception:
Which i posted to axis2-dev list and awaiting for help.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
