Since you suggested that the problem may well be with the 1.8.2 icefaces
implementation, I set up two nearly identical test webapps both running on
the latest version of Tomcat (7.0.20). One webApp used icefaces 1.8.2 and
the other one used the new icefaces 2.0.2 release. I was able to
My webapps has some icefaces pages where I need to tag on the jsessionid.
This was working in Tomcat 6.0.32 and all earlier versions but not for
Tomcat 6.0.33. It also does not work for the Tomcat 7.0.x minor editions I
have tested. It is as if the most recent Tomcat minor versions cannot tell
2011/9/12 jprideaux jpride...@snapdiagnostics.com:
My webapps has some icefaces pages where I need to tag on the jsessionid.
This was working in Tomcat 6.0.32 and all earlier versions but not for
Tomcat 6.0.33. It also does not work for the Tomcat 7.0.x minor editions I
have tested. It is
The examples as part of the 6.0.33 Tomcat deployment have both JSP and
servlets. You are right that appending a path parameter of
;jsessionid=123 works for those. What is different and specific about my
webapplication is that I am using icefaces pages which are different than
either JSP or
One other tidbit. When I call request.getRequestURI(), I get something like
PathDispatcher.service: /test3/a.iface from
org.apache.catalina.connector.RequestFacade@a245b0
when I'm using Tomcat 6.0.32
and
PathDispatcher.service: /test3/a.iface;jsessionid=blah from
2011/9/13 jprideaux jpride...@snapdiagnostics.com:
One other tidbit. When I call request.getRequestURI(), I get something like
PathDispatcher.service: /test3/a.iface from
org.apache.catalina.connector.RequestFacade@a245b0
when I'm using Tomcat 6.0.32
and
PathDispatcher.service:
2011/9/13 Konstantin Kolinko knst.koli...@gmail.com:
2011/9/13 jprideaux jpride...@snapdiagnostics.com:
Is it intended that request.getRequestURI() should return a path parameter
as part of the URI?
Yes, That is required by the Servlet Specification.
See servlet-2_5-mrel2-spec.pdf ch.
