Yes, I was able to resolve the problem. After all, the key was the "hot deployment"-releated setting for dynamic classreloading. Unfortunately the appropriate setting for this is located in three !!! different XML-configuration files (one for the WAR, one for the EAR and one for the...
After updating from WAS 4.0.2 to WAS 5.0.2 the new WAS compiles any JSP files only once. All further changes
to a JSP file are ignored - "reloading" a JSP-page inside the browser results everytime in the same (old) output.
Only stopping and restarting the appropriate AppServer makes...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.