We upgraded by executing the JahiaUpdate_4_0_4.jar file.
The only error messages is from our webapp telling us that the neither the
getRequestURI() method nor the getServletPath() method has the page attribute string from
the <jsp:forward page="/dispatcher/xxxxxController" /> in index.jsp.
(1)
index.jsp has only one line
<jsp:forward page="/dispatcher/xxxxxController" />
(2)
In web.xml we map all requests starting with "/dispatcher/*" to our one and only entry point servlet.
<servlet-mapping>
<servlet-name>DispatcherServlet</servlet-name>
<url-pattern>/dispatcher/*</url-pattern>
</servlet-mapping>
<servlet-name>DispatcherServlet</servlet-name>
<url-pattern>/dispatcher/*</url-pattern>
</servlet-mapping>
(3)
When we get a call from jahia neither the "request.getRequestURI()" method nor the "request.getServletPath()" method has the "/dispatcher/xxxxxController" string from
forwarded request.
We have used this pattern for a long time and hope that someone else has had the same problem and solved it.
In some other forums there is suggestions about the differences between
(A)
<jsp:forward page="/dispatcher/xxxxxController"/>
(B)
<jsp:include page="/dispatcher/xxxxxController"/>
(C)
<% response.sendRedirect("/dispatcher/xxxxxController");%>
(D)
<%
RequestDispatcher dispatcher = request.getRequestDispatcher("/dispatcher/xxxxxController");
dispatcher.forward(request,response);
%>
RequestDispatcher dispatcher = request.getRequestDispatcher("/dispatcher/xxxxxController");
dispatcher.forward(request,response);
%>
If I examine the generated jspservlet ..../index_jsp.java I can find
....
pageContext.forward("/dispatcher/bestallaController");
return;
return;
....
So there are different ways to "call" a servlet from a jsp-page.
I quess that Jahia calls the webapp, capture the output and prints it.
regards
/Lars
