axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Deepal Jayasinghe (JIRA)" <>
Subject [jira] Commented: (AXIS2-2380) Session scope not working
Date Mon, 16 Apr 2007 08:16:15 GMT


Deepal Jayasinghe commented on AXIS2-2380:

Hi ;
The way Axis2 soapsession works is , first you need to get the serviceGroupId to the client
side and then send that id in the next messages. But in your case you first invoke robust
operation so there is no way to get the serviceGroupId back to the client , that is why you
have encountered this problem. AFAIK that is not a bug in Axis2 , rather that is how we have
implement that. If you can get the serviceGroupId into client side (somehow) then you will
be able to invoke your service in session aware manner.

To have soapsession support, first you need to invoke in-out operation and then send that
id back in later messages.

> Session scope not working
> -------------------------
>                 Key: AXIS2-2380
>                 URL:
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Test
>          Components: deployment
>    Affects Versions: 1.1.1
>         Environment: Windows XP Service Pack2, Axis2 running as server, java 1.5.0_05
>            Reporter: Stephan Gloor
>            Priority: Blocker
> <service name="WeatherService" scope="soapsession"> ....
> doesn't work, when using the following code fragment:
> ------------------------------------------------------------------------------------
> RPCServiceClient serviceClient = 
> new RPCServiceClient(); 
> Options options 
> = serviceClient.getOptions(); 
> options.setManageSession(true); 
> ... 
> serviceClient.invokeRobust(opSetWeather, opSetWeatherArgs); 
> ------------------------------------------------------------------------------------
> the init method of the service is called every time the client executes invokeRobust
on the same serviceClient instance.
> Thanks and kind regards, Stephan Gloor, Webservices Teacher, Switzerland
> ps. would be glad to know, if this is an 1.1.1 issue - so switching to a previous version
would help.

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:
For additional commands, e-mail:

View raw message