converted to 1.6 markup
|Deletions are marked like this.||Additions are marked like this.|
|Line 5:||Line 5:|
|* Deployment: JIRA issue AXIS2-3223; [https://issues.apache.org/jira/browse/AXIS2-3223] has been opened to cover general deployment integration.||* Deployment: JIRA issue AXIS2-3223; [[https://issues.apache.org/jira/browse/AXIS2-3223]] has been opened to cover general deployment integration.|
One of the goals for Axis2 1.4 is to fully integrate JAX-WS into the current Axis2 deployment structure.
Deployment: JIRA issue AXIS2-3223; https://issues.apache.org/jira/browse/AXIS2-3223 has been opened to cover general deployment integration.
= Client =
There are some minor changes needed to get the client working optimally. These issue revolve around getting the Axis2 portions of the client properly configured. The JAX-WS 2.0 client APIs have been completely implemented, and a number of the 2.1 additions have been made as well.
ConfigurationContext: Right now there isn't a clean way to the JAX-WS client to specify the axis2.xml and repository to configure modules on the client side. There's a ConfigurationContextFactory that's exposed in the JAX-WS impl, but I this has been something for the internal impl to use thus far.
- Session management: This one may already be addressed, but I would need to do more testing in a standalone (non-Servlet Container) environment to say it's completely address.