Awesome. Can we do the same thing in 1.2?
-dain
On Jun 29, 2007, at 6:16 PM, David Jencks wrote:
This should be fixed in rev 552073. Let me know if there are more
problems.
thanks
david jencks
On Jun 29, 2007, at 11:18 AM, David Jencks wrote:
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
