I have a webapp that works fine with icefaces in my MyEclipse development environment using the integrated Tomcat sandbox. It also works find at hosting company A. We are, though, migrating it over to hosting company B and I can't get the subset of my icefaces pages to come up where I programmatically add in the jsessionid to the URL in the links. I don't do this for most of the icefaces links, but parts of the site are doing something somewhat special and need for that to work. I've also found that I can't get the icefaces pages with the jsessionid added to come up with a stand-alone Tomcat sever on my development box (although it works in MyEclipse tomcat sandbox).
Does anyone have any general guidance on what to look for. Again, it works in some environments of mine but not in others. I haven't yet been able to tell what is different. I'm using the same war file across the board.
Joined: Sep 07, 2011
I have more information about this.
Tomcat finds the iface page with the ;jsessionid added for Tomcat 6.0.32 but does not find it for Tomcat 6.0.33. Therefore, something changed between versions 6.0.32 and 6.0.33 to mess this up for me. Does anyone know what feature or security change bwtween Tomcat 6.0.32 and 6.0.33 might be responsible for the problem with adding sessionid to the URL for resources like iface pages? Also, is there a configuration change in the web.xml, server.xml, or context.xml that can turn off this change so that Tomcat 6.0.33 allows me to serve up pages like *.iface;jsessionid=123