hmm you recreated the thread? btw here was my answer: http://openejb.979440.n4.nabble.com/Re-Mutiple-module-share-the-same-container-td4657508.html
note you have to <forkMode>once</forkMode> with surefire *Romain Manni-Bucau* *Twitter: @rmannibucau* *Blog: http://rmannibucau.wordpress.com* 2012/9/19 Jean-Louis MONTEIRO <[email protected]> > Hi, > > In my opinion, it should be the target for unit tests. I mean, getting a > fresh new container for each test. > Otherwise, you can maybe focus on integration tests using our Arquillian > adapter. > > Just one question: what do you mean by "cost lots of time"? > Because, we start/stop openejb thousand of times per day and in the CI of > the project and it's not so painful. > Maybe, you are in a use case we can optimize a bit more. > > Could you share some information? > > Jean-Louis > > > 2012/9/19 xeseo <[email protected]> > > > Hi, > > In my project, several modules are under same pom project. > > Like: > > Parent (pom) > > | > > | ---- module A (jar) > > | ---- module B (jar) > > | ---- module C (jar) > > > > We're using openEJB as embeded container for unit test. However, each > > module > > will have to own its own jndi.properties, and during the Maven install > > procedure, the container will init three times and cost lots of time. > > Obviously, there will be more modules in the future. Then the test will > > cost > > more time initializing the container. > > > > So is it possible that different modules share the same container? Use > one > > centralized jndi.properties to replace all. > > Do anyone have the idea? > > > > Thanks, > > > > > > > > -- > > View this message in context: > > > http://openejb.979440.n4.nabble.com/Different-module-share-same-container-tp4657507.html > > Sent from the OpenEJB User mailing list archive at Nabble.com. > > >
