You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Jochen Schwörer <j....@web.de> on 2004/09/08 09:36:27 UTC
Sessions across different services
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
Re: Sessions across different services
Posted by Mahen Perera <ma...@gmail.com>.
if u remove it (client- config.wsdd) from the class path, does it make
a connection?
On Wed, 08 Sep 2004 15:06:36 +0200, Jochen Schwörer <j....@web.de> wrote:
> Thats not the problem. The config file is used by axis, but it does not
> make any connection.
>
> Jochen
>
>
>
> Mahen Perera wrote:
>
> > try this
> >
> > use the following java option when running the client , as in
> >
> > -Daxis.ClientConfigFile=<the Path to ur client-config file>\\client-
> > config.wsdd
> >
> > Mahen
> >
> >
> >
> > On Wed, 08 Sep 2004 14:36:30 +0200, Jochen Schwörer <j....@web.de> wrote:
> >
> >>Hi Mahen,
> >>
> >>
> >>>Joschen>> can u tell me how ur invoking the two services from the
> >>>client side. R u using Call objects? or WSDL2Java generated proxy?
> >>
> >>for testing I am using a Service and a Call object at the moment. Later
> >>I want to use WSDL2Java generated proxies.
> >>
> >>I tried to use a client-config.wsdd file which I've created with
> >>"org.apache.axis.utils.Admin client server-config.wsdd".
> >>But when placing this file into the classpath, call.invoke() doesn't
> >>make any connection to the webservice (I using tcpmon for tesing).
> >>What could be the solution to this problem?
> >>
> >>Jochen
> >>
> >
> >
>
Re: Sessions across different services
Posted by to...@gsk.com.
Well, you seem to be making progress, Jochen.
I'm surprised that reusing the engine or service didn't work. I was
looking at the 1.1. source, maybe you're using 1.2, which could be
different. According to the "Building Web Services with Java" book, the
session ID is stored in the Message Context, though that doesn't seem
right to me. The book deals with Axis 1.2, which is annoying since I have
to use Axis 1.1 and the source code for 1.1 definitely has the session ID
being stored in the current engine.
Good luck.
Tony
Hi Tony,
thanks for your investigation!
Setting the Engine object did not work. Reusing the Service neither.
But reusing the Call object works! It seems that all information about
the session is stored in the Call object.
Since I have not found a way to do this via a handler, I have to find
out, how I can merge this with the generated classes.
Many thanks for your help
Jochen
tony.q.weddle@gsk.com wrote:
> OK, Jochen. Following your reply, I had a quick look at the Axis source
> and it seems as though a new AxisClient is created for each Service
> object. The session ID is stored in the AxisClient so I guess you'd need
> to use the same Service object for all service calls. This may not be
> normal behaviour but I think it is possible. Alternatively, the Service
> object has a setEngine() method, so you might be able to get away with
> something like:
>
> nextService.setEngine(previousService.getEngine());
>
> before making the call.
>
> Tony
>
>
>
> Hi Tony,
>
> I think there is some misunderstanding. I'm requesting all services from
> the same JVM.
>
> First I create a Service and a Call object for the first service and
> then for the second.
> On the server-side I'm storing an object in the session and access it on
> each request.
> When accessing the second service, the object is not in the session
> (return value is null).
>
> Jochen
>
> tony.q.weddle@gsk.com wrote:
>
>
>>Jochen,
>>
>>I suspect that you would have to keep the client JVM alive and make all
>>service calls from that JVM, in order to maintain the session across
>>different service calls. Using the HTTP sessions might work better,
>
> though
>
>>I doubt it. Other than that, you'd probably have to write your own
>
> session
>
>>handler (maybe as a subclass of the SimpleSessionHandler) that persisted
>
>
>>the session ID on the client in some way.
>>
>>Tony
>
>
>
>
Re: Sessions across different services
Posted by Jochen Schwörer <j....@web.de>.
Hi Tony,
thanks for your investigation!
Setting the Engine object did not work. Reusing the Service neither.
But reusing the Call object works! It seems that all information about
the session is stored in the Call object.
Since I have not found a way to do this via a handler, I have to find
out, how I can merge this with the generated classes.
Many thanks for your help
Jochen
tony.q.weddle@gsk.com wrote:
> OK, Jochen. Following your reply, I had a quick look at the Axis source
> and it seems as though a new AxisClient is created for each Service
> object. The session ID is stored in the AxisClient so I guess you'd need
> to use the same Service object for all service calls. This may not be
> normal behaviour but I think it is possible. Alternatively, the Service
> object has a setEngine() method, so you might be able to get away with
> something like:
>
> nextService.setEngine(previousService.getEngine());
>
> before making the call.
>
> Tony
>
>
>
> Hi Tony,
>
> I think there is some misunderstanding. I'm requesting all services from
> the same JVM.
>
> First I create a Service and a Call object for the first service and
> then for the second.
> On the server-side I'm storing an object in the session and access it on
> each request.
> When accessing the second service, the object is not in the session
> (return value is null).
>
> Jochen
>
> tony.q.weddle@gsk.com wrote:
>
>
>>Jochen,
>>
>>I suspect that you would have to keep the client JVM alive and make all
>>service calls from that JVM, in order to maintain the session across
>>different service calls. Using the HTTP sessions might work better,
>
> though
>
>>I doubt it. Other than that, you'd probably have to write your own
>
> session
>
>>handler (maybe as a subclass of the SimpleSessionHandler) that persisted
>
>
>>the session ID on the client in some way.
>>
>>Tony
>
>
>
>
Re: Sessions across different services
Posted by to...@gsk.com.
OK, Jochen. Following your reply, I had a quick look at the Axis source
and it seems as though a new AxisClient is created for each Service
object. The session ID is stored in the AxisClient so I guess you'd need
to use the same Service object for all service calls. This may not be
normal behaviour but I think it is possible. Alternatively, the Service
object has a setEngine() method, so you might be able to get away with
something like:
nextService.setEngine(previousService.getEngine());
before making the call.
Tony
Hi Tony,
I think there is some misunderstanding. I'm requesting all services from
the same JVM.
First I create a Service and a Call object for the first service and
then for the second.
On the server-side I'm storing an object in the session and access it on
each request.
When accessing the second service, the object is not in the session
(return value is null).
Jochen
tony.q.weddle@gsk.com wrote:
> Jochen,
>
> I suspect that you would have to keep the client JVM alive and make all
> service calls from that JVM, in order to maintain the session across
> different service calls. Using the HTTP sessions might work better,
though
> I doubt it. Other than that, you'd probably have to write your own
session
> handler (maybe as a subclass of the SimpleSessionHandler) that persisted
> the session ID on the client in some way.
>
> Tony
Re: Sessions across different services
Posted by Jochen Schwörer <j....@web.de>.
Hi Tony,
I think there is some misunderstanding. I'm requesting all services from
the same JVM.
First I create a Service and a Call object for the first service and
then for the second.
On the server-side I'm storing an object in the session and access it on
each request.
When accessing the second service, the object is not in the session
(return value is null).
Jochen
tony.q.weddle@gsk.com wrote:
> Jochen,
>
> I suspect that you would have to keep the client JVM alive and make all
> service calls from that JVM, in order to maintain the session across
> different service calls. Using the HTTP sessions might work better, though
> I doubt it. Other than that, you'd probably have to write your own session
> handler (maybe as a subclass of the SimpleSessionHandler) that persisted
> the session ID on the client in some way.
>
> Tony
Re: Sessions across different services
Posted by to...@gsk.com.
Jochen,
I suspect that you would have to keep the client JVM alive and make all
service calls from that JVM, in order to maintain the session across
different service calls. Using the HTTP sessions might work better, though
I doubt it. Other than that, you'd probably have to write your own session
handler (maybe as a subclass of the SimpleSessionHandler) that persisted
the session ID on the client in some way.
Tony
Re: Sessions across different services
Posted by Jochen Schwörer <j....@web.de>.
Thanks for this tip.
After copying the part from the default config file into my specific
client-config.wsdd, the service does connect to the server again.
The I added
<requestflow>
<handler type="session"/>
</requestflow>
<responseflow>
<handler type="session"/>
</responseflow>
to each service entry (the handler is defined before <handler
name="session" type="java:org.apache.axis.handlers.SimpleSessionHandler"/>)
Now I have the same effect as without a client-config.wsdd file. The
session is maintained for each service seperatly. But what I need is a
session which spawns requests to different services.
Jochen
tony.q.weddle@gsk.com wrote:
> Jochen,
>
> Did you include the transport pivot handler that I think is specified in
> the default client-config.wsdd? That's the bit that actually sends your
> request. The client-config.wsdd default file is in the axis.jar file, in
> the org.apache.axis.client package.
>
> Tony
>
>
>
> Thats not the problem. The config file is used by axis, but it does not
> make any connection.
>
> Jochen
>
>
Re: Sessions across different services
Posted by to...@gsk.com.
Jochen,
Did you include the transport pivot handler that I think is specified in
the default client-config.wsdd? That's the bit that actually sends your
request. The client-config.wsdd default file is in the axis.jar file, in
the org.apache.axis.client package.
Tony
Thats not the problem. The config file is used by axis, but it does not
make any connection.
Jochen
Re: Sessions across different services
Posted by Jochen Schwörer <j....@web.de>.
Thats not the problem. The config file is used by axis, but it does not
make any connection.
Jochen
Mahen Perera wrote:
> try this
>
> use the following java option when running the client , as in
>
> -Daxis.ClientConfigFile=<the Path to ur client-config file>\\client-
> config.wsdd
>
> Mahen
>
>
>
> On Wed, 08 Sep 2004 14:36:30 +0200, Jochen Schwörer <j....@web.de> wrote:
>
>>Hi Mahen,
>>
>>
>>>Joschen>> can u tell me how ur invoking the two services from the
>>>client side. R u using Call objects? or WSDL2Java generated proxy?
>>
>>for testing I am using a Service and a Call object at the moment. Later
>>I want to use WSDL2Java generated proxies.
>>
>>I tried to use a client-config.wsdd file which I've created with
>>"org.apache.axis.utils.Admin client server-config.wsdd".
>>But when placing this file into the classpath, call.invoke() doesn't
>>make any connection to the webservice (I using tcpmon for tesing).
>>What could be the solution to this problem?
>>
>>Jochen
>>
>
>
Re: Sessions across different services
Posted by Mahen Perera <ma...@gmail.com>.
try this
use the following java option when running the client , as in
-Daxis.ClientConfigFile=<the Path to ur client-config file>\\client-
config.wsdd
Mahen
On Wed, 08 Sep 2004 14:36:30 +0200, Jochen Schwörer <j....@web.de> wrote:
> Hi Mahen,
>
> > Joschen>> can u tell me how ur invoking the two services from the
> > client side. R u using Call objects? or WSDL2Java generated proxy?
>
> for testing I am using a Service and a Call object at the moment. Later
> I want to use WSDL2Java generated proxies.
>
> I tried to use a client-config.wsdd file which I've created with
> "org.apache.axis.utils.Admin client server-config.wsdd".
> But when placing this file into the classpath, call.invoke() doesn't
> make any connection to the webservice (I using tcpmon for tesing).
> What could be the solution to this problem?
>
> Jochen
>
Re: Sessions across different services
Posted by Jochen Schwörer <j....@web.de>.
Hi Mahen,
> Joschen>> can u tell me how ur invoking the two services from the
> client side. R u using Call objects? or WSDL2Java generated proxy?
for testing I am using a Service and a Call object at the moment. Later
I want to use WSDL2Java generated proxies.
I tried to use a client-config.wsdd file which I've created with
"org.apache.axis.utils.Admin client server-config.wsdd".
But when placing this file into the classpath, call.invoke() doesn't
make any connection to the webservice (I using tcpmon for tesing).
What could be the solution to this problem?
Jochen
Re: Sessions across different services
Posted by Mahen Perera <ma...@gmail.com>.
Hi Jochen, Tony,
Appreciate u guys ideas.
yes, in the client-config.wsdd also we have to specify the
SimpleSessionHandler in both request flows and response flows for the
corresponding services, in order for the session management to work.
this is similar to the server-config.wsdd file.
using HTTP sessions is different from using SOAP sessions. By using
SOAP sessions, the session can be maintained and managed regardless of
the transport protocol, since whatever is the transport, the session
id will be contained in the SOAP envelope (or rather a SOAP header) ,
which is part of the payload of the transport data.
Joschen>> can u tell me how ur invoking the two services from the
client side. R u using Call objects? or WSDL2Java generated proxy?
AFAIK, the session id that the service side sends is stored in the
Axis Client Engine as a variable and since the same Axis Client
instance is used consequently by the same user, when sending the
session id back to the service side, the session id will be taken from
this variable.
take a look at the code of the SimpleSessionHandler Class ,,, this
elaborates the logic (see the comments),, may be afetr understanding
the code, u can write ur own SessionHandler, which provided the
functionality u need. However, AFAIK, the current implementation will
provide what u want I guess,
Mahen
----- Original Message -----
From: tony.q.weddle@gsk.com <to...@gsk.com>
Date: Wed, 8 Sep 2004 11:01:34 +0100
Subject: Re: Sessions across different services
To: axis-user@ws.apache.org
Hi Jochen,
>From the little I've read, you need to deploy the session handler on
the client side also. I've never done this but I believe you can use a
WSDD file on the client side to specify request and reponse handlers,
so I guess this is where you need to do it. If it already works for
one service, check out how the client is configured for that service.
Alternatively, use HTTP sessions for all services. The HTTP session is
available from the message context and the client needs to
setMaintainSession(true) on the Call or Service object.
I guess the Axis framework has to store the session cookie (which
would normally be stored by a browser) and send it with each request,
so the framework has to be told about this on the client side,
somehow.
Tony
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
tony.q.weddle@gsk.com 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 <j....@web.de>
>
> 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
>>>
>>
>>
>
>
>
Re: Sessions across different services
Posted by to...@gsk.com.
Hi Jochen,
>From the little I've read, you need to deploy the session handler on the
client side also. I've never done this but I believe you can use a WSDD
file on the client side to specify request and reponse handlers, so I
guess this is where you need to do it. If it already works for one
service, check out how the client is configured for that service.
Alternatively, use HTTP sessions for all services. The HTTP session is
available from the message context and the client needs to
setMaintainSession(true) on the Call or Service object.
I guess the Axis framework has to store the session cookie (which would
normally be stored by a browser) and send it with each request, so the
framework has to be told about this on the client side, somehow.
Tony
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
tony.q.weddle@gsk.com 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 <j....@web.de>
>
> 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
>>>
>>
>>
>
>
>
Re: Sessions across different services
Posted by Jochen Schwörer <j....@web.de>.
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
tony.q.weddle@gsk.com 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 <j....@web.de>
>
> 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
>>>
>>
>>
>
>
>
Re: Sessions across different services
Posted by to...@gsk.com.
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 <j....@web.de>
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
>>
>
>
Re: Sessions across different services
Posted by Jochen Schwörer <j....@web.de>.
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 <j....@web.de> 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
>>
>
>
Re: Sessions across different services
Posted by Mahen Perera <ma...@gmail.com>.
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 <j....@web.de> 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
>