Maybe try using the class-path: entry in your yyy_server.jar�s manifest.mf? If you have a look into the current CVS Head-Revision Source, there is a preview of the upcoming 3.0 deployer (which can be activated by uncommenting the J2eeGlobalScopeDeployer line in jboss.jcml) that will be able to deploy dependent ears/wars/jars using such class-path annotations. Best, CGJ -----Urspr�ngliche Nachricht----- Von: Jonathan Ackerman [mailto:[EMAIL PROTECTED]] Gesendet: Mittwoch, 6. Juni 2001 02:56 An: '[EMAIL PROTECTED]' Betreff: [JBoss-user] Where to put shared classes for EJBs ? Hi All, I'm currently setting up JBoss 2.2.2 into my development environment. When rolling out my applications I have come across an interesting problem. I think I know what the problem is and how to solve it but I keen on finding the most elegant way to solve the problem. The code I am deploy consists of two 'layers'. One is a framework/portal for J2EE applications, the other is an application that uses this framework. Each layer is packaged as 3 files, namely: xxx_server.jar, xxx_client.jar, xxx.war Where xxx_server.jar holds all the server (EJB) classes and xxx_client.jar holds the client classes (JavaBeans, remote & home interfaces). xxx.war is the web application and it has the xxx_client.jar file in it's WEB-INF/lib folder so it can access the JavaBeans and remote & home interfaces. So in total I have 6 files (xxx_server.jar, xxx_client.jar, xxx.war where xxx is the framework and yyy_server.jar, yyy_client.jar, yyy.war where yyy is the application) Under JBoss 2.1 this all worked fine. I dropped the xxx_server.jar & yyy_server.jar files into the "deploy" directory and installed the xxx.war & yyy.war files under tomcat. Under 2.2.2 I am now getting an java.lang.NoClassDefFoundError error during the deployment of my application (the yyy_server.jar). Now I believe this is caused by the fact that the Deployer is using now different class loaders for each module which means that my application can no longer see the classes that it needs out of the framework (Is this the real reason ???) I have come up with two solutions: 1) Include the framework classes that my application needs into its yyy_server.jar file. This is very ugly and complicates my build process. 2) Copy my xxx_client.jar file into the JBoss "lib/ext" folder. This is cleaner, but still does not sit right with me. So does anyone have any other ideas/suggestions or options ? Thanks Jonathan _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user _______________________________________________ JBoss-user mailing list [EMAIL PROTECTED] http://lists.sourceforge.net/lists/listinfo/jboss-user
