I made a small modification to the EJBTestCase so you can
use it more generically to run tests inside the appserver.
Before, it always started a UserTransaction which makes
it difficult to run tests where you want to start a
transaction yourself.
To workaround this issue, you can now say you
don't want the UserTransaction with an env-entry, e.g.
<session>
<description>JUnit Session Bean Test Runner</description>
<ejb-name>EJBTestRunnerEJB</ejb-name>
<home>org.jboss.test.util.ejb.EJBTestRunnerHome</home>
<remote>org.jboss.test.util.ejb.EJBTestRunner</remote>
<ejb-class>org.jboss.test.util.ejb.EJBTestRunnerBean</ejb-class>
<session-type>Stateless</session-type>
<transaction-type>Bean</transaction-type>
<env-entry>
<env-entry-name>NO_USER_TRANSACTION</env-entry-name>
<env-entry-type>java.lang.String</env-entry-type>
<env-entry-value>true</env-entry-value>
</env-entry>
</session>
--
xxxxxxxxxxxxxxxxxxxxxxxxxxxx
Adrian Brock
Chief Scientist
JBoss, a division of Red Hat
xxxxxxxxxxxxxxxxxxxxxxxxxxxx