Jan Luehe wrote:
Hans,
thanks for stepping in.
sorry, but I don't see which part of our email exchange you found
"very frustrating". As I said, I'm open to suggestions, and if my
patch is deemed useless, I'll revert it. No problem.
[...]
Sorry for not jumping in earlier in this discussion.
When I implemented the "shared tag libraries" feature in LiteWebServer,
I added scanning of JAR files in just /shared/lib. I do _not_ scan JAR
files in common/lib and server/lib, because placing shared tag libraries
there would be point-less; the container doesn't need access to them,
only the applications do, which is what shared/lib is for.
Maybe that cuts down the list enough so you don't have to mess with
an exclusion list at all?
good point. What about environments that embed Tomcat without following
Tomcat's directory layout, and in which the classloader hierachy/depth
is different from that in Tomcat?
I don't give them that option (with regards to this) in LiteWebServer.
The only place I look for shared libraries is $CATALINA_HOME/shared/lib.
Is that really a severe limitation, you think?
Hans
--
Hans Bergsten <[EMAIL PROTECTED]>
Gefion Software <http://www.gefionsoftware.com/>
Author of O'Reilly's "JavaServer Pages", covering JSP 1.2 and JSTL 1.0
Details at <http://TheJSPBook.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
