> that means, that the JSP and the cocoon stuff live in seperate (webapp)
> contexts (you can of course let cocoon handle JSPs). thus, the
> encodeRedirectURL can't work, of course. note though that the
> encodeRedirectURL should be done when redirecting within your webapp. for
> url rewriting base
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Im
> Auftrag von SAXESS - Hussayn Dabbous
> Gesendet: Donnerstag, 6. Februar 2003 21:07
> An: [EMAIL PROTECTED]
> Betreff: Re: AW: Session problems
>
>
> If your servlet runs
hi roberto, please see bottom of mail.
> -Ursprüngliche Nachricht-
> Von: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]Im
> Auftrag von Roberto Cipollini
> Gesendet: Freitag, 7. Februar 2003 10:16
> An: [EMAIL PROTECTED]; [EMAIL PROTECTED]
> Betreff: Re:
Unfortunatly the "encodeRedirectURL" did not work :(
It may sounds good i have crossing webapplications.
My goal is to have a single deployment of cocoon under the jakarta dir, and
store all the file of multiple virtualhosts in another directory
(/usr/webapps/.).
I got it working [maybe it'
hy,
i would like to understand, in which context your servlet is running.
Is it located within the cocoon webapp, or is it located elsewhere?
from the redirect url i guess you are crossing webapplications ...
If this is the case, you have another problem with session preserving
over multiple web
hi roberto,
the reason why your elements are empty probably are the following; the
session accessed in your XSP might be different from the JSP's session.
since you redirect without url encoding the redirect url, the session
probably doesn't survive the redirect. now in the XSP you didn't specify
