Title: Message
I
found that when working with sessions and multiple services that the session is
service based. To obtain a cross service session I had to retrieve the
session id from the service and populate it into the other services. The
session ID is just a soap header and is available
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,
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,
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 behaviou
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 sec
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 sessio
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
to each service entry (the handler is defined before )
Now I have the same effect
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
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 <[EMAIL PROTECTED]> wrote:
> Thats not the problem. The config file is used by axis, but it does not
> make any connection.
>
> Jochen
>
>
>
> Mahen Perera
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=\\client-
config.wsdd
Mahen
On Wed, 08 Sep 2004 14:36:30 +0200, Jochen Schwörer <
try this
use the following java option when running the client , as in
-Daxis.ClientConfigFile=\\client-
config.wsdd
Mahen
On Wed, 08 Sep 2004 14:36:30 +0200, Jochen Schwörer <[EMAIL PROTECTED]> wrote:
> Hi Mahen,
>
> > Joschen>> can u tell me how ur invoking the two services from the
> > cl
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 fil
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: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Wed, 8 Sep 2004 11:01:34 +0100
Subject: Re: Ses
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 serv
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.
Joc
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 ?
I think you can si
Hi Mahen,
my configuration on the server side looks like this for both services:
...
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 session
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 S
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
19 matches
Mail list logo
