Thanks for your detailed reply. I believe that there should not be any dependency with the client or how the client is sending the message. I guess it does the same way servlets getting the HTTP session details or it must be using the same methods. Let me look at these things, may be the Apache source.
Regards, Chandru. >>> <[EMAIL PROTECTED]> 02/05/02 08:29PM >>> No problem. Well, obviously the information only describes the case where Apache SOAP is being used on the server. I haven't tried yet to see what happens when the client is a non-Java or a Java but non-Apache SOAP client. Honestly I don't see why it should make any difference. When you're writing normal servlet code, you can access the HttpSession/Request/Response whether the client is C++ on Win32 or Python on FreeBSD. So these objects should still be available. The specific FAQ question addressed the question of how one could get the IP address of the client. Maybe non-Apache SOAP clients don't always give their IP address in the way expected by Apache SOAP. I don't know. What you might try is getting it working with a Java client, look at and save the actual SOAP exchange with something like proxytrace or another TCP spy. Then try with a client in your actual target language/platform, and if it doesn't work, look again at the TCP trace to see what is different. Once you see the difference, you can use SOAP messaging rather than SOAP RPC on the client to make the request look the way Apache expects, or if you have an open source SOAP implementation on the client, you could patch it. If you do, I'd suggest making the Apache-friendly behavior a parameterized behavior and submitting your work as a patch to the relevant project. I'm sure I'm not the only one on this list who would be interested in the results of your inquiries, if you choose investigate the behavior of some non-Apache SOAP libraries on the client vis-a-vis this behavior. S- "Chandrashekhar B" <[EMAIL PROTECTED]> on 02/05/2002 05:14:02 AM To: Steve Salkin/3rd/US/AON@AONNA, [EMAIL PROTECTED] cc: Subject: Re: To obtain session details [Virus Checked] Thanks for the info..FAQ says, NOTE: this will only work where the client and server are both using the Apache SOAP libraries. Is there any dependency on the client libraries, to obtain these information, if so, what kind of dependecy will that be? Regards, Chandru. >>> [EMAIL PROTECTED] 02/04/02 09:00PM >>> According to this document (http://xml.apache.org/soap/faq/faq_chawke.html) which is linked from the Apache-SOAP FAQ page (see section 2.38) if you add a SOAPContext as the first parameter of your RPC function, the server will populate it with a current SOAPContext. You can use this to get HttpSession, HttpRequest/Response handles which you can use as usual to get any information that a normal servlet would have. S- "Chandrashekhar B" <[EMAIL PROTECTED]> on 02/04/2002 08:06:54 AM Please respond to [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: (bcc: Steve Salkin/3rd/US/AON) Subject: To obtain session details [Virus Checked] Hi All, Is there a way for an application method or methods that have registered into the SOAP server to know the session details, like if the request has come over SSL or not, what is the authentication scheme used by the web server, the domain from where the request came from etc., In general, is there a way the SOAP server/servlet can pass some information to its registered methods, Thanks in advance, Chandru.
