Hallo!

I'm newbie to axis, and have just tested some things, i.e. how to deploy wsdd files among other things. I saw that there are both server side deployment and client side deployment of wsdds. On the server side, it will be deployed to the server-config.xml, and it also works at me. But what happens in case of client side wsdds? I tried to deploy a client side wsdd with the handler SimpleSessionHandler (from axis), but nothing happend (I put the session_id into the MessageContext). Is there a configuration xml for the client, as well?

Actually I would like to write a server application (sessioned, over http), where the user can log in, and then they can call the services. On the client site when the user logs in, gets a session id that can be used for further communication. (I need a session-ed communication)
for example on the client side, there would be the following functions

Client client = new Client(url)
String sessionid = client.login(user, passw);
client.somefunction(sessionid, someparams);

I thought that I should have 2 handlers: Authentication Handler, Session handler (for example SimpleSessionHandler), (and maybe Authorization handler).
Is this approach  ok?

Is ist possible to create client, wsdl automatically so that when calling a function (service), then also the soap-headers are created? (at login the authentication header, when using sessionid, then the seeion header).
Thanx for the answers in advance

Georg





--
Using Opera's revolutionary e-mail client: http://www.opera.com/m2/

Reply via email to