In http://portals.apache.org/wsrp4j/arch/consumer.html it says, "The generated SOAP stubs are doing the cookie handling and are caching the cookies in instance variables. This means that one stub object instance is equivalent to one HTTP session which we map to one WSRP session (initCookie wise)"
By sniffing the requests and responses' headers for the rpc calls, I verified that the cookies are indeed cached and passed for any subsequent request for that session. So, to answer my original question - Yes, WSRP4J do handle cookies by itself. However, I didn't find the code in the Stub implementation that does that. Can somebody enlighten me as to, where does caching of cookies happen? Is it something that the Stub configures to tell Axis to cache cookies? May be maintainSession=true does that? I can look more deep into it but I was thinking if someone knows it already. Thanks Abhishek. On Wed, Mar 26, 2008 at 12:02 PM, Abhishek Shadangi <[EMAIL PROTECTED]> wrote: > Hi All, > > When Producer specifies requireInitCookie to non-none value, WSRP4J calls > initCookie() in the MarkupInterface. But I am not sure how does WSRP4J > handle the cookies that Producer sets in the HTTP response after the > initCookie() call is made. Is th job of the Consumer (that uses WSRP4J) to > handle it, if Yes HOW, or is it the handled within WSRP4j itself? > > Please help. Any ideas or comments would be highly appreciated! > > Thanks > Abhishek. > >
