Axis2 - a few improvements to support handlerchain
--------------------------------------------------
Key: GERONIMO-2947
URL: https://issues.apache.org/jira/browse/GERONIMO-2947
Project: Geronimo
Issue Type: Improvement
Security Level: public (Regular issues)
Components: webservices
Affects Versions: 2.0
Environment: winxp + sun 1.5 SDK
Reporter: Lin Sun
Fix For: 2.0
Hi,
This is a working-in-progress patch that contains the following improvements to
the handlerchain support:
1) updated the handlerchain test and a few other handler improvements Jarek did
recently for Axis2.
2) add a Axis2Util class to help getting serviceQName, portQName and
EndpointDescription from axisService.
3) add missing license statements in different files.
4) Provide an PortInfoImpl class...this is a temp solution. Need to use the
PortInfoImpl class from Axis2 and ask Axis2 to make the contructor public (will
log an axis2 jira on that).
5) Create a BindingImpl object and set the handlerchain on it, passed the
BindingImpl object to Axis2 by
msgContext.setProperty(JAXWSMessageReceiver.PARAM_BINDING, binding);
but I still don't see the handleMessage below got called by Axis2 when running
jaxws-war:
public boolean handleMessage(SOAPMessageContext smc) {
System.out.println(this + " handleMessage(): " + greeting);
return true;
}
I expect to see a
[EMAIL PROTECTED] handleMessage(): Hello
after the post construct of the handler. Comments/suggestions are welcome and
needed!:-)
Lin
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
