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
[EMAIL PROTECTED] 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
[EMAIL PROTECTED] 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
