To Barry, you mean the AW in the subject? this is the German Re. Just showing that its an answer. Re stands for Reply AW stands for Antwort.
To Klaus, Why do you think that something gows wrong on server side? If you deployed your server with that line and you set the maintainsession to true, the Session should be working. I see this in my tcpmon, which shows me the current session-ID in the SOAP-header. What is it like at your architecture? For me it looks like this: I instantiate a ServiceLocator, set for this the maintainsession to true, build service from the locator and invoke methods. Together with the deploying on the server-side I can now see a line like: Cookie: JSESSIONID=........ in my SOAP-Header. For every invoke this ID is equal so it indicates me, that the session is working. But since now I'm not able to append Objects to that session, because I always got a NullPointer, when I try. I will try to use the SimpleSessionHandler on client side to manage that problem and will tell how that works. Greetings from Hamburg/Germany -----Ursprüngliche Nachricht----- Von: Klaus Thiele [mailto:[EMAIL PROTECTED]] Gesendet: Montag, 16. Dezember 2002 10:20 An: [EMAIL PROTECTED] Betreff: Re: AW: AW: Deploying the client Hi Sebastian, > <parameter name="scope" value="Session"/> i'm already doing this. i'd like to something like this: public interface PersdatSoap { public boolean signon(String uid); public PersdatSoapData read(); public void write(PersdatSoapData data); public Collection cmb_land(); } java org.apache.axis.wsdl.Java2WSDL -o PersdatSoap.wsdl -lhttp://localhost:8080/axis/services/PersdatSoap com.PIAG.soap.test.PersdatSoap and java org.apache.axis.wsdl.WSDL2Java -o . --deployScope session --server-side --skeletonDeploy true PersdatSoap.wsdl in the implementation i do some initializations in the signon-method: - getting a reference to an stateful sessionbean,... and store it to _instance_ variables. at the next calls to the other methods, i try to use the instance var's and -oops- each call generates a new session (and a new instance of the service)?!?! (but i deployed with <parameter name="scope" value="session"/>!!!) after changeing the _client_ code: PersdatSoapServiceLocator sl = new PersdatSoapServiceLocator(); sl.setMaintainSession(true); ^^^^^^^^^^^^^^^^^^^^^^^^^ it works as expected! ok. this my be a temporary solution for an only axis/java environment, but i think, anything goes wrong at server-side with '<parameter name="scope" value="session"/>'!? klaus Am Freitag, 13. Dezember 2002 17:25 schrieb [EMAIL PROTECTED]: > Hi Klaus, > > maybe we can help each other.... > > to configure the session on server-side is rather easy I think (I can > just think because actually I didnt get it working since now, because > of the client side): Just add the line <parameter name="scope" > value="Session"/> to the service-description in your > server-config.wsdd. That should be everything. And in the tcpmon you > then have Set-Cookie-line inside the SOAP-Header, where the session-ID > is shown. > > To the client-side: Why does wsdl2java generate a deploy.wsdd-file for > you? do you add a '-s' to the command line: java > org.apache.axis.wsdl.WSDL2Java --deployScope Session ? If not: whats > exactly the command-line you are using with wsdl2java? And how do you > include the deploy.wsdd-file in your client? Or do you just do > nothing? [...] -- Klaus Thiele - Personal & Informatik AG mailto:[EMAIL PROTECTED] "There's got to be more to life than compile-and-go."
