John, George and Jordan,<div><br></div><div>I'm assuming that both the JMS and JCR modules will want to leverage the transaction support for non-EJBs that is currently provided by Seam Persistence, correct? Given that's the case, I proposed moving the transaction APIs into the org.jboss.seam.transaction package. However, after Seam 3.0 final, I'm thinking we should split this package into a transaction module that can be shared. Does that sound like the right way to go?</div>
<div><br></div><div><a href="https://issues.jboss.org/browse/SEAMPERSIST-34">https://issues.jboss.org/browse/SEAMPERSIST-34</a></div><div><br></div><div>Btw, you can use an @Unwraps method or proxy handler to enlist your resource into the current transaction when the resource is dereferenced. See <a href="https://github.com/seam/persistence/blob/master/impl/src/main/java/org/jboss/seam/persistence/ManagedPersistenceContextProxyHandler.java">https://github.com/seam/persistence/blob/master/impl/src/main/java/org/jboss/seam/persistence/ManagedPersistenceContextProxyHandler.java</a></div>
<div><br></div><div>-Dan<br clear="all"><br>-- <br><div>Dan Allen</div>Principal Software Engineer, Red Hat | Author of Seam in Action<br>Registered Linux User #231597<br><br><div><a href="http://www.google.com/profiles/dan.j.allen#about" target="_blank">http://www.google.com/profiles/dan.j.allen#about</a><br>
<a href="http://mojavelinux.com" target="_blank">http://mojavelinux.com</a><br><a href="http://mojavelinux.com/seaminaction" target="_blank">http://mojavelinux.com/seaminaction</a><br></div><br>
</div>