JAXWS: Make server side code use new Message Model APIs
-------------------------------------------------------
Key: AXIS2-950
URL: http://issues.apache.org/jira/browse/AXIS2-950
Project: Apache Axis 2.0 (Axis2)
Issue Type: Improvement
Components: jaxws
Reporter: Nick Gallardo
I've done some work to refactor the server side components so that we're no
longer using the org.apache.axis2.jaxws.parameter.* APIs. Those will be going
away soon and all JAX-WS code should be using the
org.apache.axis2.jaxws.message.* APIs for handling data.
Along with adding more comments and trace, I've made the following changes:
- Changed the method signature for the ProviderDispatcher (and the
EndpointDispatcher interface) to take a MessageContext. This will be needed
further down the road when we are required to support the @WebServiceContext
annotation on the target endpoints.
- Changed the EndpointController so that it is a stateless entity. Some of the
information that it was using is now pushed down to the ProviderDispatcher
specifically. The EndpointController shouldn't touch the message other than to
make sure it's set on the MessageContext. The job of reading the Message and
deciding on a course of action is up to the particular EndpointDispatcher
implementation.
- Changed the JAXWSMessageReceiver to mirror the client side in its usage of
the InvocationContext/MessageContext APIs.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
