[
https://issues.apache.org/jira/browse/AXIS2-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bill Nagy resolved AXIS2-3547.
------------------------------
Resolution: Invalid
I've tried out a number of scenarios, and a JAX-WS client and service are able
to utilize HTTP sessions correctly. The JAX-WS spec does not talk about
sessions beyond being able to participate in an HTTP session (i.e. being able
to set/extract things in the Servlet context,) so further integration with the
Axis2 session model is not required for compliance with the spec.
> JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer
> with Simple JAXWS client
> ---------------------------------------------------------------------------------------------------
>
> Key: AXIS2-3547
> URL: https://issues.apache.org/jira/browse/AXIS2-3547
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Reporter: Davanum Srinivas
> Assignee: Bill Nagy
> Priority: Blocker
> Fix For: 1.4
>
>
> Looks like the JAXWS Sessions scenarios need work.
> - JAXWS Service inside Tomcat/Axis2 should be able to participate in a
> transport session
> - JAXWS Service inside SimpleAxisServer/Axis2 should be able to participate
> in a transport session
> These services should be able to work with
> - Standalone Axis2/ADB client with sessions enabled.
> - JAXWS Client with sessions enabled.
> thanks.,
> dims
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
