2 things: 1.) Tomcat doesn't use your system's classpath variable. It's got it's own class loaders.
2.) Starting with Tomcat 5.5 you won't need to install a full jdk as this version ships with it's own compiler. So, things should get easier. On Thu, 2004-10-21 at 20:08, Luke FERNANDEZ wrote: > I've run into the problem of the JSP 2.0- Examples not rendering in the last two > installs I've done of Tomcat. > > On the last install I resolved the problem by: > > --removing all of the JDKs and JREs through Windows Settings > Remove Programs, > --removing any j2sdk folders > -- reinstalling the jdk which created a j2sdk1.4.2_05 folder. > --pointing the environmental variable JAVA_HOME to the j2sdk1.4.2_05 folder > > After doing all that the JSP 2.0 examples worked. > > I'm not sure why the extra JRE and JDK installations were running > interference....I'd think that if JAVA_HOME was pointing to the j2sdk1.4.2_05 any > other jars that are lying around wouldn't matter..... maybe my environment CLASSPATH > variable was pointing to a different JRE and that overode the JAVA_HOME setting? I > dunno....but starting from a clean install definitely seemed to help. > > Although I like Java and find it challenging to program in, I find the installation > of a Java development environment sometimes unfuriatingly difficult with all the > classpath gotchas. There really should be a way of designing a less fragile > installation that isnt as contingent on everything else being just so. Introductory > texts on Java programming like to talk up all the benefits of encapsulation and I > guess they've been incorporated into the language. But when it comes to a Tomcat > install it seems that encapsulation wasn't given much attention * at least if > encapusalation means insulation from outside environments. Is this a sensible > impression or maybe I'm misunderstanding something? > > Cheers, > > Luke > > > > >>> [EMAIL PROTECTED] 10/21/2004 4:41:14 PM >>> > > > --On Thursday, October 21, 2004 10:03:17 AM -0400 "Shapira, Yoav" > <[EMAIL PROTECTED]> wrote: > > > > This usually indicates multiple versions of either the JSP APIs or the > > Jasper classes on the server's runtime classpath. I hope when you > > upgraded your server you did an installation to a clean directory, not > > an overwrite of the old directory. If you did the latter, search it for > > jsp.jar and jsp-api.jar and make sure only one is present: the latest. > > Same thing for the Jasper jars (jasper-compiler, jasper-runtime, etc.). > > > > Yoav > > > > Yes, the install was into a clean directory. There is only one each of the > two jasper jars, and no jsp.jar or jsp-api.jar in the installation directory > (or in the download zip file jakarta-tomcat-4.1.31.zip) Are those two jars > supposed to be included?? The only place I even find the jsp jars is in the > Eclipse and MyEclipse toolkits. Eclipse is an IDE, and I'm bringing up > tomcat (at least initially) outside of the IDE. > > Are these two jsp jars something I should have and so I should go get them > seperately from the tomcat distro? And where should they go? > > Thanks, > Rob > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
