Does Jasper use the Context Classpath when compiling JSP's?
Greetings! I know there are two (or three) different classpaths within Tomcat 3.2. I asked this question on tomcat-user last week, but no one knew the answer. The question is, does Jasper, when compiling JSP files, use the Context Classpath, which referrs to the WEB-INF/classes directory for that specific JSP? If not, how could I add the Context Classpath to the Jasper code? Can someone point me to a breakdown of the classloading within Jasper specifically? I've seen the classloading for Servlets, and that is all kosher. Thank you in advance for any tips, pointers, or direction. Will -- /~'find `funny quote`': Command not found; humor not installed. 1986 Concours 72,xxx CDA #00046 COG AMA Overland Park, KS [EMAIL PROTECTED] PCS: 316-371-FOAD http://will.mylanders.com/
Does Jasper use the Context Classloader for Compiling JSP files?
Greetings! I know there are two (or three) different classpaths within Tomcat 3.2. The question is, does Jasper, when compiling JSP files, use the Context Classpath, which referrs to the WEB-INF/classes directory for that specific JSP? If not, how could I add the Context Classpath to the Jasper code? Can someone point me to a breakdown of the classloading within Jasper specifically? I've seen the classloading for Servlets, and that is all kosher. Thank you in advance for any tips, pointers, or direction. Will -- /~'find `funny quote`': Command not found; humor not installed. 1986 Concours 72,xxx CDA #00046 COG AMA Overland Park, KS [EMAIL PROTECTED] PCS: 316-371-FOAD http://will.mylanders.com/
Re: [DOC] Re: [3.2] JSP Compiling Classpath issues -- finding WEB-INF/class es
On Fri, 20 Jul 2001, Craig R. McClanahan wrote: On Fri, 20 Jul 2001, Rob S. wrote: A, maybe I should add this to the INSTALL.txt file - unset your CLASSPATH before starting TC? I've logged into my fair share of *nix boxes where the admins have conveniently set a system-wide CLASSPATH containing an XML parser, etc. The standard Tomcat 4 startup scripts already ignore your CLASSPATH variable, and reconstruct one tuned to its needs. If you want to make application classes available to all web apps, put them (unpacked) into $CATALINA_HOME/classes or in JAR files under $CATALINA_HOME/lib. So, does that cross-apply to having all of your classes from /classes and /lib available for the JSP's to use when being compiled by Jasper? Will
Re: [3.2] JSP Compiling Classpath issues -- finding WEB-INF/classes
On Thu, 19 Jul 2001, David Rees wrote: (Sorry about the double-qoute, I missed the original message) I have noticed the same problem while doing some development using Tomcat 3.2.[23]. I worked around it by making sure that I unset the classpath before calling startup.sh, then things seemed to work properly and classes were found as expected. Tried that. Tried hard-coding the classpath. If the web applications WEB-INF/classes directory was in the system classpath, it compiles. If it is not in the system classpath, the JSP's do not compile. So, why does Jasper not know about the web-application classpath? Will
RE: [3.2] JSP Compiling Classpath issues -- finding WEB-INF/classes
On Fri, 20 Jul 2001, Andrew McGhee wrote: Guys, I've copied in an email returned to a support desk regarding a problem similar to this. There is a link to mikal.org that explains it in better detail, but essentially it refers to where your classes are found, as to what classloader they inherit. And the solution we found (similar to the post) is to ensure your classpath is unset before starting Tomcat. The solution posted (unset your classpath, cause there might be a class with the same name somewhere else) is fine for first year university students. Most likely, that *is* what causes their problems. grin But, I have set, unset, hard coded, soft coded and so on the classpath. In tomcat.sh, I have a hard-coded classpath pointing to the .jar files in TOMCAT_HOME/lib, and tools.jar. Nothing else. I try to hit a JSP for the first time, the compile fails. Jasper reports that it cannot find classes that are located in the web applications WEB-INF/classes directory. Theoretically, the adaptive classloader should know about WEB-INF/classes, and I thought Jaspter used the adaptive classloader. If I change the hard-coded classpath in tomcat.sh to point to the web applications WEB-INF/classes directory, so that the WEB-INF/classes folder is in the system classpath, Jasper can now find the classes and compilation continues normally. Can one of the developers detail out where Jasper looks for classes for compiling JSPs? Thanks for any tips or suggestions! Will
[3.2] JSP Compiling Classpath issues -- finding WEB-INF/classes
Greetings! Over on tomcat-users, theres been a discussion on JSP's finding the WEB-INF/classes directory when compiling. They can't. From searches, I understand this issue has come up before in regards to the Coocon project. The root problem is that Jasper cannot find classes located in WEB-INF/classes of the web application that the JSP's belong to. This occurs when a JSP is either first deployed or the TOMCAT_HOME/work directory is cleared, requiring a recompile of the JSP's. The system is Tomcat 3.2 under Apache with mod_jk, running on SunOS 2.7 with JDK 1.2. The code in question is coming from a production Tomcat 3.1 system. I cannot add the WEB-INF/classes directory to my classpath. This will break several other parts of the system. What is the problem with Jasper reading WEB-INF/classes? I understand the the Coocon users found some kind of workaround, but I have been unable to find it. Thank you for any pointers or tips! Will -- /~'find `funny quote`': Command not found; humor not installed. 1986 Concours 72,xxx 1982 Maxim 12,xxx (For Sale!) CDA #00046 Overland Park, KS [EMAIL PROTECTED] PCS: 316-371-FOAD http://will.mylanders.com/
