On Oct 25, 2009, at 11:59 AM, Horacy Oliwka wrote:
It seems like spring's classloaders ignore WEB-INF/lib, except when
spring.jar is also there, but I'd like to have spring.jar in a global
directory.
yes, this is exactly what happens. classloaders can look up the
chain of classloaders,
where'd you get that idea? unless things have changed very
dramatically since 3.1.6 (the version I'm using) you can put database
drivers in WEB-INF/lib just fine.
I don't know a simple way to find out the location from which classes
are loaded. I agree -- that could be quite useful.
If
exceptions like these pretty much always (in fact always?) indicate a
mismatch between the compilation and runtime environments. A method
that existed when the code was compiled doesn't exist when the code is
run.
in this case, that method
(ReflectionUtils.makeAccessible(Constructor))
On Mar 10, 2009, at 7:14 AM, Aaron Freeman wrote:
Why use Apache at all?
you may have a situation where you haven't got a single webapp, but
many webapps and other creatures living under a single host. in that
case apache makes a nice top-level dispatcher, proxying requests to
the
