Hi Peter,
I would expect that the return of the JSESSIONID cookie header in the
response is performed by some sort of response filter at a layer below
that of Jersey (e.g. at the servlet layer).
Jersey just writes the response (it does not matter if a custom
provider is used or not to do the writing) to the servlet output
stream. I am guessing that because something has been written to the
response output stream that the underlying filter can no longer set
the JSESSIONID cookie header. Perhaps you could verify with a simple
servlet? sorry i cannot be of much more help.
Paul.
On May 8, 2009, at 4:18 PM, Peter Coppens wrote:
>
> Hello,
>
> I am using Jersey 1.0 (jersey-bundle-1.0.jar) and I have a problem
> when I
> try to 'logon' using spring security (in tomcat)
>
> I implemented the logon as PUT of a credentials resource and it
> works fine
> if the PUT method does not return a response. Once the PUT method does
> return a resource (even a String) the JSESSIONID cookie is not
> returned
>
> E.g.
>
> @PUT()
> public void login(CredentialsResource credentials) {
>
> works fine
>
> but
>
> @PUT()
> public CredentialsResource login(CredentialsResource credentials) {
>
> fails...that is the call is fine, the CredentialsResource is
> returned fine
> but the cookie is no longer in the reply header.
>
> Note, not sure it is relevant, I use a custom provider
>
> Any help warmly welcomed!
>
> Peter
>
> --
> View this message in context: http://n2.nabble.com/JSESSION-cookie-not-returned-with-Spring-Jersey-integration-tp2845573p2845573.html
> Sent from the Jersey mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_jersey.dev.java.net
> For additional commands, e-mail: users-help_at_jersey.dev.java.net
>