You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2006/07/11 21:58:32 UTC

[jira] Resolved: (AXIS2-881) JAXWS: Refactoring invocation APIs

     [ http://issues.apache.org/jira/browse/AXIS2-881?page=all ]
     
Rich Scheuerle resolved AXIS2-881:
----------------------------------

    Resolution: Fixed

(Visible to axis2-developers)


> JAXWS: Refactoring invocation APIs
> ----------------------------------
>
>          Key: AXIS2-881
>          URL: http://issues.apache.org/jira/browse/AXIS2-881
>      Project: Apache Axis 2.0 (Axis2)
>         Type: New Feature

>   Components: jaxws
>     Reporter: Nick Gallardo
>     Assignee: Rich Scheuerle

>
> I've started work on refactoring the lower-level invocation APIs for JAX-WS.  Right now, the Dispatch and dynamic proxy implementations use the AxisController API to perform the invocation.  I'd like to maintain the same general concept, but clean the APIs up a bit and moving some of the function around to more apporpriate places.
> Also included in this will be the first pass at the MessageContext(s) defined in the JAX-WS spec.  This will delegate down to the Axis2 MessageContext wherever possible.  This includes the SoapMessageContext and the LogicalMessageContext as well.

-- 
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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org