> 2) Add those search paths myself, in my webapp's code. Keep in
> mind that, as
> Rob S. speculated, I know very little about the ClassLoader mechanism.
When I wrote the email, I wasn't implying that whatsoever, but I can see
quite clearly now how it could be taken. Apologies for that implication...
Ok, let me get this straight now. You're saying, "i want to point a web app
to a location to load jars and classes from." That already exists. You put
the jars in the WEB-INF/classes and lib directory.
Then the next thing is, "i want them to be visible to more than one web
app." That already exists too. You put them in $CATALINE_HOME/common/lib
and classes.
What do you want that Tomcat isn't already giving you? =)
- r
