geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <david_jen...@yahoo.com>
Subject Re: Transaction manager now tied to ejb?
Date Fri, 29 Jun 2007 18:18:47 GMT
This is an easy fix, thanks for noticing the problem... just need a  
little more testing before I commit...

thanks
david jencks

On Jun 28, 2007, at 6:03 PM, Dain Sundstrom wrote:

> It appears that the geronimo transaction manager is now tied  
> directly to ejb :(  The TransactionManagerImpl class has the  
> following code:
>
>     public void setEntityManager(String persistenceUnit, Object  
> entityManager) {
>         Object oldEntityManager = entityManagers.put 
> (persistenceUnit, entityManager);
>         if (oldEntityManager != null) {
>             throw new EJBException("EntityManager " +  
> oldEntityManager + " for persistenceUnit " + persistenceUnit + "  
> already associated with this transaction " + xid);
>         }
>     }
>
> This makes it very difficult for me to use the tm manager in light- 
> weight environments. Can we remove all the JPA and EJB related  
> stuff from the TransactionManager classes (and module).  I was able  
> to implement all of the JPA required functionality in OpenEJB  
> without needing to modify the transaction manager.
>
> In the mean time I'll drop back to using the 1.x transaction manager.
>
> -dain


Mime
View raw message