Girish,
No -- Call.getMessageContext().getProperty("JSESSIONID") returned a NULL.
So I dumped all the propertynames in the MessageContext after the return
from invoke() and got this ...
************************
Dumping out the properties names in the message context
transport.url
transport.http.statusMessage
transport.http.statusCode
call_object
wsdl.service
RPC
************************
I dug deeper into each property -- dumping out it's contents ... but
did not see any cookies (or HTTP request/response objects) anywhere.
Conrad
-------- Original Message --------
Subject: RE: accessing the HTTP Headers in the Response
Date: Wed, 20 Aug 2003 17:29:15 -0400
From: "Manchaiah, Girish (LNG-DAY)" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: "'[EMAIL PROTECTED]'" <[EMAIL PROTECTED]>
Call.getMessageContext().getProperty(cookieName);
-----Original Message-----
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 20, 2003 5:01 PM
To: [EMAIL PROTECTED]
Subject: accessing the HTTP Headers in the Response
All,
I need to access the HTTP headers in the response after the
call.invoke().
Specifically, I need to get the JSESSIONID (cookie) that the web server
sets.
This is to code a work around for a load balancer which does not
understand
SOAP Headers.
I have been through the API (and chased my tail pursuing different
paths).
However, there does not appear to be an easy way to access the HTTP
Headers
from the Call (or Service) object.
Since the transport is HTTP, don't we have access to the HTTP Request
and
Response objects?
Any body faced this situation? Any ideas on a workaround?
Thanks
Conrad
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
--------------------------------------------------------------------
mail2web - Check your email from the web at
http://mail2web.com/ .
