[
https://issues.apache.org/jira/browse/AXIS2-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574673#action_12574673
]
Nick Gallardo commented on AXIS2-3547:
--------------------------------------
For the Tomcat scenario, if the endpoint calls getSession() or getSession(true)
on the HttpServletRequest object, then it should trigger the servlet container
to send back the necessary info.
The question then becomes a question of whether or not the right info (cookie
or URL re-write) is sent and consumed.
I don't know how that endpoint mechanism aligns with the SimpleAxisServer
though.
> 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
> 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]
