axis-java-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Alex Burmester <...@beast.com>
Subject Re: AW: accessing HTTP cookies
Date Fri, 09 Jul 2004 17:04:39 GMT
The fix is currently not in the 1.2 codebase but it has been 
offered that if someone tweaks the 1.1 patch to work against the latest
cvs code, they will check it in.  I was planning on doing this but I 
haven't had any free time the past few weeks.

On Fri, 9 Jul 2004, Christian Campo wrote:

> hi alex,
> that is exactly the problem I am having. Thanks a lot.
> Jira does not say anything about a fix version. Anybody knows if that
> bug will be fixed in 1.2. ???
> thanks
> christian
> 
> On Thu, 8 Jul 2004 11:36:54 -0700 (PDT), Alex Burmester <adb@beast.com> wrote:
> > As far as I know the current versions of axis do not support
> > multiple cookies.  You might have a look at
> > http://issues.apache.org/jira/browse/AXIS-1080
> > 
> > Alex.
> > 
> > 
> > 
> > On Thu, 8 Jul 2004, Christian Campo wrote:
> > 
> > > not quite....
> > > setProperty(HEADER_COOKIE,"ssoid=xyz");
> > > setProperty(HEADER_COOKIE2,"plid="abc");
> > > This would result in the HTTP headers:
> > >
> > > Cookie: ssoid=xyz
> > > Cookie2: plid=abc
> > >
> > > But thats not what Cookie2 is for. I am not absolutly sure what
> > > Cookie2 is for, but it is for new version of Cookie-management. (as
> > > far as I can tell)
> > >
> > > What I need are headers like these
> > >
> > > Cookie: ssoid=xyz
> > > Cookie: plid=abc
> > >
> > > And yes you can set multiple Cookies in one call but since the call
> > > object SETs cookies and does not allow to manage several cookies (as
> > > an array) this is the source of the problem.
> > >
> > > christian
> > >
> > > On Thu, 8 Jul 2004 13:59:37 +0200 , Dorner Thomas
> > > <thomas.dorner@edmb.debis.com> wrote:
> > > > Ok,
> > > >
> > > > you can set first cookie: with setProperty(Heaer_Cookie, "");
> > > > and second cookie: with setProperty(Header_Cookie2, "");
> > > >
> > > > back .....(Header_set_Cookie,"");
> > > >
> > > > Is it?
> > > >
> > > > Tomi
> > > >
> > > > -----Ursprüngliche Nachricht-----
> > > > Von: Christian Campo [mailto:christian.campo@gmail.com]
> > > > Gesendet: Donnerstag, 8. Juli 2004 13:57
> > > > An: axis-user@ws.apache.org
> > > > Betreff: Re: accessing HTTP cookies
> > > >
> > > > Hi,
> > > > thanks for trying to sort this out. But setScopedProperty ist a
> > > > deprecated method (that will be removed soon according to the apiDoc).
> > > > Also it only sets a local property for that call object.
> > > >
> > > > I am looking for a way to supply 2 cookies with 2 different names that
> > > > are not the standard JSESSIONID name which should then be passed to
> > > > the webservice. And of course every now and then a Set-Cookie header
> > > > comes back and I would look to pick it up then and set it in some
> > > > local var.
> > > >
> > > > Still looking for a solution.
> > > > christian campo
> > > >
> > > > ----- Original Message -----
> > > > From: Daniel Amadei <danielamadei@yahoo.com.br>
> > > > Date: Thu, 8 Jul 2004 08:21:09 -0300 (ART)
> > > > Subject: Re: accessing HTTP cookies
> > > > To: axis-user@ws.apache.org
> > > >
> > > > Hi!
> > > >
> > > > I set cookies in the response using the following statement:
> > > >
> > > > call.setScopedProperty(HTTPConstants.HEADER_COOKIE, cookie);
> > > >
> > > > Maybe there is something similar for getting the request cookie.
> > > >
> > > > []'s
> > > >
> > > > Daniel Amadei
> > > >
> > > > Christian Campo <christian.campo@gmail.com> wrote:
> > > >
> > > > Hi everyone,
> > > >
> > > > I want to use cookies to maintain session state in the client
> > > > application that I am currently building. However Axis, to hide
> > > > transport details from the application, I guess does not directly
> > > > allow to access the cookies that were transported in a call.
> > > >
> > > > I am using the dynamic Call Object and do not use generated stubs. On
> > > > the serverside I found that it is possible to write a global request
> > > > handle that can "pull" the httpservletrequest object and get the
> > > > cookie from their.
> > > >
> > > > However on the client side the cookie object is very well hidden. The
> > > > only current solution that we have is accessing private fields using
> > > > reflection (which of course only works without a SecurityManager).
> > > >
> > > > Anybody can help me here ???
> > > >
> > > > BTW: The reason why we choose Cookies and not SOAP Headers is because
> > > > we use the same mechanism for browser
> > > >  applications and have some
> > > > central components which are managing and checking the session are not
> > > > aware of the difference between a webapplication and a webservice. So
> > > > Cookies is a mechanism that works in both worlds.
> > > >
> > > > thanks
> > > > --
> > > > christian campo
> > > >
> > > >                 ________________________________
> > > > Yahoo! Mail agora ainda melhor: 100MB, anti-spam e antivírus grátis!
> > > >
> > > >
> > > > --
> > > > christian campo (gmail.com)
> > > >
> > >
> > >
> > >
> > 
> > 
> 
> 
> 


Mime
View raw message