You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tomcat.apache.org by Navneet Karnani <na...@myrealbox.com> on 2005/04/07 10:23:08 UTC

Re: Moving jsp from development environment (v 5.0.28) to production environment (5.5.7) leads to complilation problems

> Note however, that the error message is wrong. If I strip a lot of the code
> at the bottom of the jsp file, it'll compile with the exact same first
> couple of lines.
I figure this to be the problem with the compilet that Tomcat is using. 
Try and make the JDK (sun compiler) as the default for tomcat. This was 
the default in 5.0 in 5.5 they moved to the JDT compilet. This may fix 
the problem.

- Navneet
> 
> I also have Tomcat 5.5.7 installed on my development box, but the same thing
> happens there. As a workaround, I compiled the jsp inside Netbeans, then put
> the generated .java and .class files in the appropriate path on the
> productive system, and that takes care of the problem, yet it means for the
> slightest change of the jsp page, I have to recompile and move all 3 files
> over to the productive machine.
> 
> Is there a solution to this? I figure for some wicked reason, Tomcat has
> problems with certain .jsp files but so far I have not been able to find
> anything that the files that cannot be compiled have in common with the ones
> that can be compiled.. Depending on how much I remove from the jsp, it will
> compile on Tomcat 5.5.7, but I'm afraid I cannot find the logic behind when
> it'll compile and when it won't so I'm hoping somebody else has an idea.
> 
> Regards
> Stephan


---------------------------------------------------------------------
To unsubscribe, e-mail: tomcat-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: tomcat-user-help@jakarta.apache.org