I have done some more investigations and figured out that the problem is that we get a call to our servlet but the servlet can not find the correct servletPath or URI. The correct servlet path is the one which index.jsp forwards to. Currently it gets the original index.jsp?
My current theori is that some jahia servlet wrapper or request wrapper is doing something wrong here. It may be in the call from jahia to our webapp. It may also be a tomcat issue. Jahia version compared to tomcat version. Can we find any information about the "best" jahia -tomcat combinations?
Of course we will continue and try a clean 4.0.4 or 4.0.5 installation but ou problem is that we only get this strange behaviour on the public web-site. We have at least ten development and test-installations and we have never got this problem before. It showed up when we upgraded the "real"-site.
This week we will deploy an important struts-application. I am very curious about what will happen if a struts-application can not read the servlet-path with the 'action'.do part?
regards
/lars hagrot
