The answer depends in part on what you mean by "an id of who is invoking the call."
Many services are implemented with a client id as a parameter to every method call. Google does this. You could design your services similarly. If you specifically want to use sessions based on HTTP cookies, you are correct that you want to access session info. You can do this with RPC. Look at http://ws.apache.org/soap/docs/guide/migration.html, the section titled <Getting at "environmental" information for RPC style services>. However, I must point out that many SOAP implementations do not, by default, maintain sessions on the client, and some implementations cannot maintain sessions at all. If you will have an "open" client base (i.e. you will not specify the way the clients are implemented), you should not assume that sessions based on HTTP cookies will be supported. --- [EMAIL PROTECTED] wrote: > Hi, > > I would like to know how, using soap rpc, could I > determine (from the service > side) an id of who is invoking the call. > > I have seen that using soap messages, with the > SOAPContext(request-context) > of the incoming message, I could use the method > getProperty with the constant > org.apache.soap.Constants.BAG_HTTPSESSION, to obtain > an object from the > class javax.servlet.http.HttpSession, and then to > obtain the id of the http > session from there. But I would like to know if I > could do something like > that with soap rpc. > > Thanks a lot, > > Tizo > > ===== Scott Nichol __________________________________ Do you Yahoo!? Yahoo! SiteBuilder - Free web site building tool. Try it! http://webhosting.yahoo.com/ps/sb/
