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 "Davanum Srinivas (JIRA)" <ji...@apache.org> on 2008/02/26 05:19:51 UTC

[jira] Created: (AXIS2-3547) JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer with Simple JAXWS client

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


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


[jira] Commented: (AXIS2-3547) JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer with Simple JAXWS client

Posted by "Nick Gallardo (JIRA)" <ji...@apache.org>.
    [ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Commented: (AXIS2-3547) JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer with Simple JAXWS client

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12572353#action_12572353 ] 

Davanum Srinivas commented on AXIS2-3547:
-----------------------------------------

FYI, AxisService created by the JAXWSDeployer has the default scope set to SCOPE_REQUEST.

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


[jira] Updated: (AXIS2-3547) JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer with Simple JAXWS client

Posted by "Nick Gallardo (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Gallardo updated AXIS2-3547:
---------------------------------

    Priority: Blocker  (was: Major)

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


[jira] Resolved: (AXIS2-3547) JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer with Simple JAXWS client

Posted by "Bill Nagy (JIRA)" <ji...@apache.org>.
     [ 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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org


[jira] Updated: (AXIS2-3547) JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer with Simple JAXWS client

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/AXIS2-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Davanum Srinivas updated AXIS2-3547:
------------------------------------

    Fix Version/s: 1.4
         Assignee: Bill Nagy

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


[jira] Commented: (AXIS2-3547) JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer with Simple JAXWS client

Posted by "Davanum Srinivas (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/AXIS2-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12574674#action_12574674 ] 

Davanum Srinivas commented on AXIS2-3547:
-----------------------------------------

Guess we need to at least support tomcat (for the tck work)

-- dims

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