Re: [Springframework-developer] JAR file separation and classloader issues

[Rod J. <rod...@in...>]

> As noted in build.xml, this could be made obsolete by using the thread
context class loader within the framework, for loading classes and other
resources like bundles. I've already prototyped this, it's simple and seems
to work nicely. Note that it is advisable to keep the Spring JARs in your
application lib directory anyway, you won't be confronted with these
problems in any case then. There's no choice, of course, ifyour application
server uses the EJB classloader as parent of your web app classloader -
though this should work equally well with the thread context approach.

Are you proposing changing to context loader? I think it's probably a good
idea, as otherwise I suspect we may encounter ongoing problems. I can't
envisage any problems with context loading (although I'm sure any approach
will fail in some servers without code changes :-)

While your packaging sounds logical, maybe this would enable simpler
packaging. But I guess the "skeleton" approach could show what Jars were
needed for EJB apps etc.

Regards,
Rod