Tomcat classloader issues with spring, jsf and corba

amy

Hi,

I currently stuck in the tomcat 6 classloaders nightmare (seems to me).
Having a web application with jsf-1.2-ri, spring, log4j, visibroker corba orb, corba-orb-services, serlvet-filters, some own generic-application-spring-beans and some spring beans belonging to the web-application.

If I deployed all of the jars into my WEB-INF/lib then the Java 5 ORB.init(..) method is not able to locate the ORB-implementation classes because it sits in the web-apps lib and the Java ORB (loaded by the system class loader) does not see classes in my web-app.

If I deployed the visibroker corba-orb to tomcat's shared loader the corba-orb-service which are installed during ORB.init is not found.

If I deployed the corba-orb-service to tomcat's shared loader the required log4j classes and spring are not found.

If I deployed log4j and spring to tomcat's shared loader then the jsf-ri could not be found.

Finally I deployed all classes to tomcat's shared loader but now there is only one log4j Logger instance for all web-applications there (and I can change the log level for other web-applications).

My question is how will system-wide classes deal with dynamic classloading via introspection where the dynamically loaded classes reside in the web-app directory ?

IMHO must be such a quot;classloader-callbackquot; to the web-app classloader if tomcat's shared loader is looking for classes.

I wonder how spring is able to instantiate beans where the bean class also sits in the web-app?????????

Any suggestions?

TIA