Thanks for the idea! I hadn't considered that. We could do that. However, I think it would have a big impact on performance; we would need to use remote interfaces instead of local ones and, since our deployments are scoped, we'd have to turn on Call-By-Value option in JBoss which I understand would also affect performance.
I think that would rule this option out. Thanks, Lloyd. -----Original Message----- From: Adam Hardy [mailto:[EMAIL PROTECTED] Sent: 29 July 2005 16:51 To: Maven Users List Subject: Re: Maven, EJBs and clashing JNDI names Lloyd Davies on 29/07/05 12:28, wrote: > My company have recently migrated their java projects from Ant to Maven. > It's has all gone pretty smoothly until now. > > > > We have a number of components, including ears, ejb-jars, jars etc. 2 of my > ears contain the same ejb jar file. I would like to deploy both of these > ears to the same instance of JBoss but I can't because the jndi names for > the EJBs inside the common ejb-jar files are the same and therefore clash on > deployment. > > Can anyone tell me how I can handle this without breaking Maven's best > practices and making the 2 copies of the ejb-jar file different? Can you seperate out that EJB into its own EAR? --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.338 / Virus Database: 267.9.7/60 - Release Date: 28/07/2005 --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
