> 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 based sessions, this appends the ';JSESSIONID=...' to the url. > so, not doing this causes losing the session then. > > so what can you do? from the top of my head two ideas: > > 1. let cocoon handle the JSPs > 2. deliver the parameters (username/pw) via request parameters/attributes > (don't know if the latter works, though). >
Well, the second idea works fine as i've already tested it and...guess what? there are 2 different indipendent session. I put user/pwd values in the session first in the check_login.jsp page, and then send them via form/action/post/submit to the cocoon environment to let them be stored in the session of coccon. In this way, i got two session with the same values that i can retrieve in tomcat or cocoon as for my needs. This system looks like a bit "non pro". it's just a way of getting round the obstacle. i don't know if this is the right way. The first idea seems likely the most useful, but i really CANT have my jsp be compiled inside the cocoon env. Just to understand my system i use redhat8, tomcat 4.0.4 and cocoon 2.0.3 I've tryed to have a jsp page be served by cocoon but i got a 505 server error page....what a tricky situation :) ill keep on trying.... see ya later thanks. Roberto --------------------------------------------------------------------- Please check that your question has not already been answered in the FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html> To unsubscribe, e-mail: <[EMAIL PROTECTED]> For additional commands, e-mail: <[EMAIL PROTECTED]>
