We already have Tomcat 4.1.18 talking well to Weblogic 5.1, and it was quite the event of tearing jars et al apart and getting them placed in the proper spots of the classloader hierarchy.
I'm now struggling with trying to do the same integration of Tomcat 4.1.18 to Weblogic 8.1, and it's not going well at all. What is interesting at this stage is that our default startup servlet runs and can get access to the EJB server (it caches a bunch of stuff from the EJB side on startup). I've already got "select" portions of the weblogic.jar from both in shared/lib and on the system classpath, mostly from trial and error. I've had to move my EJB interface classes (Like BeanSession, and BeanSessionHome) out of the web app and into the system classpath, as well as any classes that THEY reference. "You're in a maze of twisty ClassLoaders, all alike..." I've gotten a simple standalone client app working, so it's pretty clear to be the complicated class loader environment of the Tomcat that's tripping me up here. Any help at all would be welcome. The hole in my wall, monitor and desk is ever expanding and my head Really hurts... Thanx! Regards, Will Hartung ([EMAIL PROTECTED]) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
