|
Aside from the fact that it does not work
in certain situations, why would you think it is not a good idea to put
your app specific libs under the WEB-INF\lib directory.
The spec says to do it. It allows for good
application orginization. What would be your arguments against
it?
Actually I can think of one argument against it,
and that is that by including your libs in the classpath instead, you can
control the order of the classpath. It appears that using the libs
directory would allow for random ordering (based on OS directory ordering) of
these libs. Also, I need to include zip files and these don't get picked
up anyway. Maybe using the classpath is the way to go.
Bill Pfeiffer
----- Original Message -----
|
- Re: jar's still not picked up in WEB-INF/lib Bill Pfeiffer
- Re: jar's still not picked up in WEB-INF/lib Leon Palermo
- Re: jar's still not picked up in WEB-INF/lib Bill Pfeiffer
- RE: jar's still not picked up in WEB-INF/lib Raghu Havaldar
- Re: jar's still not picked up in WEB-INF/lib Bill Pfeiffer
- Re: jar's still not picked up in WEB-INF/lib Leon Palermo
- Re: jar's still not picked up in WEB-INF/l... Martin Smith
- Re: jar's still not picked up in WEB-INF/l... Bill Pfeiffer
- RE: jar's still not picked up in WEB-INF/lib Raghu Havaldar
- Re: jar's still not picked up in WEB-INF/lib Bill Pfeiffer
- RE: jar's still not picked up in WEB-INF/lib Raghu Havaldar
- RE: jar's still not picked up in WEB-INF/lib Lagrue, John
- I just built mod_jk.so on linux John Elia
- Re: jar's still not picked up in WEB-INF/lib Leon Palermo
