Jess Holle wrote:
>No, unfortunately I have no small test case. Our JSPs are the opposite
>
>of standalone test cases and I've not had time to try to find a trigger
>
>within them -- and quite likely won't have such time.
Fair enough. If you do find time, that would be great.
Mark
-
No, unfortunately I have no small test case. Our JSPs are the opposite
of standalone test cases and I've not had time to try to find a trigger
within them -- and quite likely won't have such time.
Out of our 1000's of JSP pages I saw a dozen or so JSP precompilation
failures that weren't pres
Jess Holle wrote:
>I moved to Tomcat 7.0.34 -- apparently with inadequate testing / too
>much trust.
>
>Some JSPs that precompiled just fine with 7.0.33 and many previous
>Tomcat versions now produce the error shown below
>
>Moving back to the ecj jar from Tomcat 7.0.33 resolves the issue. I'm
I moved to Tomcat 7.0.34 -- apparently with inadequate testing / too
much trust.
Some JSPs that precompiled just fine with 7.0.33 and many previous
Tomcat versions now produce the error shown below
Moving back to the ecj jar from Tomcat 7.0.33 resolves the issue. I'm
assuming buggy JDT compi
