Serge Huber <shuber2 <at> jahia.com> writes: > > > Hi Miriam,
> - you might also run into issues with the session. By linking directly > to the servlet, you will most probably loose the session (unless you are > using a special configuration with Tomcat 5.5). This is due to the fact > that before Tomcat 5.5 sessions are not shared across web application > contexts (Tomcat 5.5 introduces a new configuration option that allows > this, more info here : > http://weblogs.java.net/blog/wholder/archive/2005/02/session_session.html > ). Hello again, This is only to confirm that I've understood correctly what is happening because after getting Tomcat 5.5.9 get working with Jahia, I have the same problem: If I click directly to the servlet, I still loose the session. Is it neccesary to send the session to the servlet controller in some way? I explain the steps: Suppose that I'm logged into webmail and I want to see a mail that has an image attachment: 1.- I click in the message I want to see and message.jsp page is called. This jsp page (if an attachment is included) calls a method of class X, which returns something like <img border="0" src="/webmail/jwma?acton=message&todo=displaypart&number=0"> (because I haven't used encodeURL method, so servlet is directly called). 2.- jwma is the controller servlet and according to the parameters, its displaypart method should be called, but before it an exception is thrown because the servlet "thinks" that the user is not authentificated and it redirects you to login again. Is is neccesary to pass the session from class X to controller servlet in some way? I supposed that thanks to new configuration of Tomcat 5.5, this was not necessary. Thanks again for any idea... Miriam
