On Jul 29, 2010, at 6:23 PM, dmitry.shu...@travelunderwriters.com wrote: > Hi Jean-Louis, > > Thanks for prompt reply! > > Our old system used the JBoss embedded for testing, so it was a first > candidate to try and immediately we discovered following issue: > > https://jira.jboss.org/browse/JBIDE-6464?page=com.atlassian.jira.plugin.ext.subversion%3Asubversion-commits-tabpanel > > Basically it tries to deploy the same EJM multiple times if it is > presented in several jars (or the same jar is presented in multiple > places). > > Before I start with OpenEJB config It is good to verify how OpenEJB will > behave in such situation, will it fail the entire deployment of ignore it?
By default we deploy anything in the classpath that has a descriptor. If you have the "same" persistence unit (by same I mean several units with the same name) then we deploy them all without conflict. The EE spec only requires that unit names be unique within a persistence.xml, reusing a unit name in other jars is allowed but the units are still considered different and all must be deployed. That's the default, but things in the classpath can be filtered out: http://openejb.apache.org/3.0/application-discovery-via-the-classpath.html As well you can supply alternate descriptors for specific testing scenarios: http://openejb.apache.org/3.0/alternate-descriptors.html And of course the fallback is we're more than happy to add features or do what we can to make things easier for people. -David > > From: > Jean-Louis MONTEIRO <jean-louis.monte...@atosorigin.com> > To: > users@openejb.apache.org > Date: > 29/07/2010 02:46 AM > Subject: > Re: Bootstraping multiple EAR's > > > > > Hi Dmitry, > > I can't see anything preventing such a usage. > You can add deployment directories/files in the openejb.xml file. > > Give it a try and feel free to push a new message in case of troubles. > > Jean-Louis > -- > View this message in context: > http://openejb.979440.n4.nabble.com/Bootstraping-multiple-EAR-s-tp2305811p2306227.html > > Sent from the OpenEJB User mailing list archive at Nabble.com. > >