maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thorsten Heit" <th...@gmx.de>
Subject Re: eclipse and maven discrepancies
Date Fri, 30 Mar 2007 13:27:50 GMT
Hi Rolf,
> The errors i get are in the target/surefire-report dir in two files.
> i give the contents of the xml file

*snip*

>     <failure type="javax.naming.NameNotFoundException"
> message="EntityManagerFactories not bound">
> javax.naming.NameNotFoundException: EntityManagerFactories not bound
>     at org.jnp.server.NamingServer.getBinding(NamingServer.java:529)
>     at org.jnp.server.NamingServer.getBinding(NamingServer.java:537)
>     at org.jnp.server.NamingServer.getObject(NamingServer.java:543)
>     at org.jnp.server.NamingServer.lookup(NamingServer.java:267)
>     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:626)
>     at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:588)
>     at javax.naming.InitialContext.lookup(InitialContext.java:351)
>     at auction.test.EJB3IntegrationTest.getEntityManagerFactory(
> EJB3IntegrationTest.java:133)
>     at auction.test.basic.PersistentStateTransitions.withoutEJBContainer(
> PersistentStateTransitions.java:53)
> </failure>
>   </testcase>
>   <testcase time="0" name="withEJBContainer">
>     <failure type="javax.transaction.NotSupportedException"
> message="Transaction already active, cannot nest transactions.">
> javax.transaction.NotSupportedException: Transaction already active,
> cannot
> nest transactions.
>     at org.jboss.tm.TxManager.begin(TxManager.java:557)
>     at org.jboss.ejb3.embedded.UserTransactionImpl.begin(
> UserTransactionImpl.java:74)
>     at auction.test.basic.PersistentStateTransitions.withEJBContainer(
> PersistentStateTransitions.java:116)
> </failure>

*snip*

> It looks like the embedded container doesn't have what it needs to startup
> properly but I don't have a clue what to look for

See the last message: There's still a transaction open in the actual tested class that isn't
closed when the next test method is executed. Are you using overwritten implementations of
#setUp() and #tearDown() in that test class?

Have you tried using different fork mode for your tests?
(see http://maven.apache.org/plugins/maven-surefire-plugin/examples/forking.html)


HTH

Thorsten

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org


Mime
View raw message