Hi Tony,
yes, I did define the handler "session".
Sessions are working for *one* service without problems. But I want to get the same session from another service.
I think there must be some configuration on the client side to tell the axis engine to use the same sessionID for all services.
Jochen
[EMAIL PROTECTED] wrote:
Jochen,
I've only read a little about sessions but I think you have to deploy the SimpleSessionHandler on the client's request and response flows. I don't know if you need to do this on the server. Also, did you define the handler type "session" before refering to it in your <requestflow>?
I think you can simply use the HTTP sessions instead, without deploying any handlers.
Tony
Hi Mahen,
my configuration on the server side looks like this for both services: <service name="SomeService" provider="java:RPC" style="wrapped"> ... <requestflow> <handler type="session"/> </requestflow> <responseflow> <handler type="session"/> </responseflow> </service>
When watching the request/responses with TcpMon, I see that when I query the 2nd service for the first time, the client does not pass the previous received sessionID.
Any further ideas?
Jochen
Mahen Perera wrote:
Hi Jochen
Have u put the SimpleSessionHandler in both request flows and response flows in both the services?
If this is so , there will not be a problem I guess.
And see whether ur sending the same session id from the client side when invoking both services , using tcpmon.
Mahen
On Wed, 08 Sep 2004 09:36:27 +0200, Jochen Schwörer <[EMAIL PROTECTED]>
wrote:
Hi,
I have successfully configured sessions for one service with the SimpleSessionHandler.
Now I've noticed that the session is only valid for one service. Ie if I connect to one service (eg. AuthenticationService) which stores some objects in the session, these objects are not visible from the other service (eg. WorkerService).
Is there any possibility to maintain one session per client for all services? And if yes, which configuration is necessary?
regards Jochen Schwoerer
