You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by "Samisa Abeysinghe (JIRA)" <ji...@apache.org> on 2006/04/14 07:20:00 UTC

[jira] Created: (AXIS2C-128) service skeleton invoke need to have message context as a parameter

service skeleton invoke need to have message context as a parameter
-------------------------------------------------------------------

         Key: AXIS2C-128
         URL: http://issues.apache.org/jira/browse/AXIS2C-128
     Project: Axis2-C
        Type: Improvement

  Components: core/receivers  
    Versions: Current (Nightly)    
    Reporter: Samisa Abeysinghe
    Priority: Critical
     Fix For: 0.91


When trying to test WSA on the server side I found out the need of passing the message context to the invoke method of service skeleton. Without this I am unable to set the out going WSA action, which is different from incomming WSA action from the service implementation.

Furthermore we would need this feature for session handling in service groups.

-- 
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


[jira] Assigned: (AXIS2C-128) service skeleton invoke need to have message context as a parameter

Posted by "Samisa Abeysinghe (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2C-128?page=all ]

Samisa Abeysinghe reassigned AXIS2C-128:
----------------------------------------

    Assign To: Samisa Abeysinghe

> service skeleton invoke need to have message context as a parameter
> -------------------------------------------------------------------
>
>          Key: AXIS2C-128
>          URL: http://issues.apache.org/jira/browse/AXIS2C-128
>      Project: Axis2-C
>         Type: Improvement

>   Components: core/receivers
>     Versions: Current (Nightly)
>     Reporter: Samisa Abeysinghe
>     Assignee: Samisa Abeysinghe
>     Priority: Critical
>      Fix For: 0.91

>
> When trying to test WSA on the server side I found out the need of passing the message context to the invoke method of service skeleton. Without this I am unable to set the out going WSA action, which is different from incomming WSA action from the service implementation.
> Furthermore we would need this feature for session handling in service groups.

-- 
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


[jira] Closed: (AXIS2C-128) service skeleton invoke need to have message context as a parameter

Posted by "Samisa Abeysinghe (JIRA)" <ji...@apache.org>.
     [ http://issues.apache.org/jira/browse/AXIS2C-128?page=all ]
     
Samisa Abeysinghe closed AXIS2C-128:
------------------------------------

    Resolution: Fixed

Added message context as a parameter so that service implementation can manipulate it.
Updated the samples as well.

> service skeleton invoke need to have message context as a parameter
> -------------------------------------------------------------------
>
>          Key: AXIS2C-128
>          URL: http://issues.apache.org/jira/browse/AXIS2C-128
>      Project: Axis2-C
>         Type: Improvement

>   Components: core/receivers
>     Versions: Current (Nightly)
>     Reporter: Samisa Abeysinghe
>     Assignee: Samisa Abeysinghe
>     Priority: Critical
>      Fix For: 0.91

>
> When trying to test WSA on the server side I found out the need of passing the message context to the invoke method of service skeleton. Without this I am unable to set the out going WSA action, which is different from incomming WSA action from the service implementation.
> Furthermore we would need this feature for session handling in service groups.

-- 
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