[seam-dev] declarative transactions for jms and jcr

[George Gastaldi]

Nice, I agree that it is the right way to go. I was almost suggesting
separating that on a separate module also.

However it must be considered that JTA would not always be used (when
running on tomcat for example). How would this module handle these scenarios
? Would it depend on persistence module itself ?

Em 11/03/2011, às 21:54, Dan Allen <dan.j.allen at gmail.com> escreveu:

John, George and Jordan,

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?

https://issues.jboss.org/browse/SEAMPERSIST-34

Btw, you can use an @Unwraps method or proxy handler to enlist your resource
into the current transaction when the resource is dereferenced. See
https://github.com/seam/persistence/blob/master/impl/src/main/java/org/jboss/seam/persistence/ManagedPersistenceContextProxyHandler.java

-Dan

-- 
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597

http://www.google.com/profiles/dan.j.allen#about
http://mojavelinux.com
http://mojavelinux.com/seaminaction

 _______________________________________________
seam-dev mailing list
seam-dev at lists.jboss.org
https://lists.jboss.org/mailman/listinfo/seam-dev
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/seam-dev/attachments/20110311/d3330c0c/attachment.html