To work with session scope in a .NET client, the client must be able to accept a cookie. All you need to do is to add a CookieContainer to your service client class. Use the following code (C#) :

some.url.of.service.someService myService = new some.url.of.service.someService() ;
myService.CookieContainer = new System.Net.CookieContainer() ;

(substituse your web reference class for "some.url.of.service.someService")

--Barry

BTW - what does AW: mean?

Klaus Thiele wrote:

Hi Sebastian,

i'm new to axis an i'm currently working at this problem too.

java org.apache.axis.wsdl.WSDL2Java --deployScope Session
writes
<parameter name="scope" value="Session"/>
to deploy.wsdd - but it seems that it hasn't any effect.

in my client i do MyServiceLocator sl = new MyServiceLocator();
sl.setMaintainSession(true);
and then it works with session.

but how to enable this at server-side? it's not nice to set this at client-side, i'm also testing with .NET and don't know how to enable this there.

klaus

Am Freitag, 13. Dezember 2002 16:26 schrieb [EMAIL PROTECTED]:

Hi Pascal,

[...]

But I have another question. I need to work with session. What I know is
(or what I think I know): I need to define the scope of the service to
session, and I have to invoke the SessionHandler during request and
response flow. But: I think I have to define request and response-flow on
both sides; the client and the server. But in the wsdl-file there is no
entry for that flow-definitions I defined for the service on server-side.
If I really have to tell the client-side axis to invoke my Handler (i.e.
the SimpleSessionHandler) in request and response: How do I tell him
without including a wsdd-file? Or do I have to define other stuff to get
this working?

[...]

--
Klaus Thiele - Personal & Informatik AG
mailto:[EMAIL PROTECTED]

"There's got to be more to life than compile-and-go."




Reply via email to