Janap schrieb:
Thank you for the reply. I do not precompile my JSP's . Anyways I made a complete clean build in Eclipse. The problem still persists.
I'm not talking about explicitly precompiled JSPs.
When precompilation is not used, servlet engines (eg tomcat) compile JSPs into java, then java into .class files "on demand", ie as the jsps are accessed. And the servlet engine caches these .java and .class files in a "work" directory so they can be reused as long as the .jsp file doesn't change.
But if you then change the tag implementations (ie install a jar that has new implementations of tag classes) then the servlet engine doesn't know that it should discard its cached versions. So it is necessary to remove this "work" directory manually. Not doing this after updating a lib containing jsp tags causes all sorts of weird problem.
I don't know how this works with whatever Eclipse/servlet-engine integration you are using, but I bet there is still a "work" directory around somewhere that holds cached compiled jsp files.
Regards, Simon
