SeamTest and Embedded EJB questions

[jschuetter]

Hi there,

I have some question concerning integration tests with Seam.

1) I have the impression the MDB configuration is not picked up by EJB bootstrap initiated through SeamTest. On container startup I get an "DefaultJMSProvider not bound" error
If I bootstrap the EJB container myself and specifically deploy the XML files it works fine. If I let SeamTest bootstrap the container I can't control these deployments, can I?

2) Is bootstrapping the EJB container myself a viable way or must SeamTest start up the container?

3) Do I have to bootstrap the EJB container again for each SeamTest I run ? If I bootstrap the container myself and run a second SeamTest, Seam will initialize the components again. The tests run fine as far as I can see but I get a warning:
[AbstractSeamPhaseListener] There should only be one Seam phase listener per application

Thanks
Jens

[jschuetter]

I resolved issue 1) now. I had to copy the content of jboss-jms-beans.xml into jboss-beans.xml so it gets picked up by SeamTest. That means jboss-jms-beans.xml in the Seam embedded-ejb/conf folder is not read on container start-up though.

Jens

[marcioendo]

2) I have been bootstrapping the EJB Container myself and setting the org.jboss.seam.core.Ejb to false in components.xml.

[jschuetter]

I bootstrapped it the container on its own as well. But if you test several SeamTest classes it will still rescan the components every time and complain about several phase listeners, right?
Ok it comes to question 3) then ..

Jens

[marcioendo]

Good point. This could be related to the problem I am having with SeamTest and the new 1.1BETA1 version.

I guess one could simply override the SeamTest.init() method and Annotate it with @Configuration(beforeSuite = true) instead of the @Configuration(beforeTestClass = true). Don't know how if TestNG handles this nicely.

I will probably try this tomorrow or later today.

[jschuetter]

yes I guess that could work I might try this as well even though changing the Seam code to speed up the tests is not my preferred solution ..

jens