[seam-issues] [JBoss JIRA] Commented: (SEAMPERSIST-15) Expose TransactionWork as an API

Dan Allen (JIRA) jira-events at lists.jboss.org
Tue Dec 21 13:28:20 EST 2010


    [ https://issues.jboss.org/browse/SEAMPERSIST-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12571715#comment-12571715 ] 

Dan Allen commented on SEAMPERSIST-15:
--------------------------------------

I've attached an API as a proposal, which is a bit more attractive than the current internal work helper in the persist module.

https://gist.github.com/750328

I'm open to other suggestions. I'm not sure the TransactionContext is necessary, though it does open up the possibility of giving access to an EntityManager instance of choice. It could be injected into the consumer bean instead. 


> Expose TransactionWork as an API
> --------------------------------
>
>                 Key: SEAMPERSIST-15
>                 URL: https://issues.jboss.org/browse/SEAMPERSIST-15
>             Project: Seam Persistence and Transactions
>          Issue Type: Feature Request
>    Affects Versions: 3.0.0.Beta1
>            Reporter: Dan Allen
>
> Seam persist provides transaction APIs that are generally useful independent of a transactional bean. However, setting transaction boundaries still requires some work. We see this even inside the persist module, where transactional "work" is wrapped in a helper. I propose exposing this worker as a utility, either for extension writers or for uses in an application.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        


More information about the seam-issues mailing list