Well, I believe in your EJB you only need dependencies to compile your code, the JARs will not be included in your EJB, are they? In that case you define, in the dependencies of your EJB, the <scope>provided</scope>, which makes these objects non-transitive for your webapp...
ejb: .... <dependency> <groupId>something.group</groupId> <artifactId>something-else<artifactId> <scope>provided</provided> </dependency> .... This will make your EJB compile and everything. webapp: .... <dependency> <groupId>ejb.groupId</groupId> <artifactId>ejb-name<artifactId> <type>ejb-client</type> </dependency> .... This should include the ejb-client into your webapp WITHOUT its dependencies. Unless you want something else on the EJB-level, this is the way I think you should go... Roland On Friday 09 June 2006 15:45, Todd Nine wrote: > Thanks for the excludes and provided suggestion, but I'm not sure they'll > help. The jars I want excluded aren't part of the EJB,they're dependencies > and transitive dependencies of the EJB, not classes in the EJB project. > Roland, I'm not sure I understand your 'provided' method, can you > elaborate? > > Thanks, > Todd > > On 6/7/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> > > wrote: > > The EJB 2.1-SNAPSHOT (not sure if it's been released) includes a > > 'clientExcludes' directive that can be added as a subelement of the > > generateClient element... > > > > ... > > <generateClient>true</generateClient> > > <clientExcludes> > > <clientExclude>**/appversion.properties</clientExclude> > > <clientExclude>**/test/**/*.*</clientExclude> > > </clientExcludes> > > ... > > > > > > > > -----Original Message----- > > From: Todd Nine [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, June 07, 2006 11:49 AM > > To: [email protected] > > Subject: EJB Client dependencies > > > > Hi all, > > I'm declaring an EJB client with the following decencies in a webapp, > > and the common interfaces and beans for parameters and return values > > > > > > <dependency> > > <groupId>ata.partnership</groupId> > > <artifactId>partnershipCommon</artifactId> > > <version>1.0.0-SNAPSHOT</version> > > </dependency> > > <dependency> > > <groupId>ata.partnership</groupId> > > <artifactId>partnershipEJB</artifactId> > > <version>1.0.0-SNAPSHOT</version> > > <type>ejb-client</type> > > </dependency> > > > > This works for requiring the EJB client, however, I'm also receiving > > partnershipBusiness, partnershipDataAccess, etc etc. These are all > > required in my EJB, but I don't want these transitive dependencies to be > > deployed on the remote client (The webapp). Short of an excludes > > directive in the webapp when I declare the ejb client dependency, is > > there any parameter I can use in the EJB plugin to exclude all decencies > > of the EJB on the client side when I build the ejb client? > > > > Thanks, > > Todd > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
