I have a cautionary tale for anyone who has an existing app with a web
component and an ejb component that runs with tomcat and jboss :
With the release of the J2eeDeployer and the EmbeddedTomcatService my
App stopped working completely. I started getting
ClassNotFoundExceptions thrown when my jsps were accessed. It made no
sense as the app ran fine with tomcat and jboss in either separate vms
or with the existing TomcatService module. It even ran with the
pre-release version of the EmdeddedTomcatSevice that required the code
change to Tomcat 3.2Beta. I having been pulling my hair out trying to
figure out what was going wrong.
I finally figured out what it was. It was how I have been packaging my
war file and ejb-jar file. It turns out that I have been a bit lapse in
what class files I include in both of these. My web app use a mvc jsp
framework called struts. To use it you have to include a jar file in the
lib directory of the war file. You write your own code that extends some
of the classes in this lib jar file. This was my problem. I included (by
accident) some of these child classes in my ejb-jar. When my jsps tried
to load them I got ClassNotFoundExcpetions thrown becuase of the
relationship (I assume) between the EJB container classloader and the
webapp classloader. By removing these classes file from the ejb-jar file
fixed the problem.
Moral of the story : Be careful how you package the jar, war and ear
files.
Richard Backhouse
Oak grove Software
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Problems?: [EMAIL PROTECTED]
