Out of curiosity, maybe I've been working with tomcat for too long, but isn't loading jar's from webapp/lib a standard of the servlet spec?
Eric W Hauser wrote:
Resin won't load from the webapp/lib directory unless you turn on the classloader hack. I've been using the following method of defining jars specific to a webapp with a lot of success (in web.xml):
<classpath id="/path/to/jarfile.jar" />
Also if you to add a whole directory:
<classpath id="/path/to/jarfile.jar" library-dir="true" />
Keep in mind that this won't work if you decide not to use Resin. You can add this to resin.conf as well if you want to load jars after the system classloader.
If you are just using the core and fmt tag library, I would recommended just using Resin's internal implementation. I've used it without any problems.
On Thu, 15 Jan 2004, Dennis Warren wrote:
This was going to be my last resort. I think I might have to give it a try because I'm having absolutely no luck. I've tried to put classes on the classpath, put classes in the jdk extension directory, and defining them in resin.conf. I'll have to see how this turns out.
Thanks for all the suggestions guys.
-Dennis
Kris Schneider wrote:
Does this still apply:
<http-server> <servlet-classloader-hack>true</servlet-classloader-hack> </http-server>
Quoting Hans Bergsten <[EMAIL PROTECTED]>:
Dennis Warren wrote:
yes, there's a tag to disable that in Resin 2.1 but it doesn't seem to resolve my problem.
<caucho.com> <http-server> <jsp fast-jstl='false'/> ... </http-server> </caucho.com>
I keep getting the error message below. DocumentRange.class is supposed to be xalan.jar which is contained in WEB-INF/lib of the standard-examples web-app. Is there anything in JDK1.4.2 that is overriding this?
Most likely, Resin doesn't use the XML classes from WEB-INF/lib and instead uses the JDK versions, so if the version bundled with JDK 1.4.2 no longer has this class, you would get this type of error.
Tomcat has an "endorsed" directory for dealing with things like this, and I believe Sun's JDK also have a flag for pointing to a directory that holds replacements for "extensions" bundled with the JDK (such as the XML classes). You may want to see if Resin has something similar, or see if you can get it to use the "java" command flag to pick up the Xalan version distributed as part of the JSTL implementation.
I hope this helps. Incompatible changes in the XML classes between releases combined with class loader schemes is very frustrating ...
Hans
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
------------------- Eric Hauser [EMAIL PROTECTED] (317) 679-4766
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
