well actually I think it is linked to your setup. Closing container is important but using both works well on our build on I used it a lot for business projects. That said if a test doesnt handle correctly its lifecycle you can get unpredictable behavior when running next one (two start will just make the second one reuse old context for instance) Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau
2014-04-15 18:06 GMT+02:00 amber <[email protected]>: > For the null, error, we have to explicit close the ejbcontainer : > > init : > ... > ejbcontainer = EJBContainer.createEJBContainer(p); > ... > > @AfterClass > public static void stop() { > if (context != null) { > context.close(); > ejbcontainer.close(); > } > } > > works fine on one module Maven, but on another still some tests failure only > with eclipse (ok with Maven)... > > Working with both openEJb embedd and jaxrs seems .. not easy ? > > > > > > > > -- > View this message in context: > http://openejb.979440.n4.nabble.com/OpenEJB-testing-REST-services-tp4668791p4668798.html > Sent from the OpenEJB User mailing list archive at Nabble.com.
