[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2022) split transaction enablement into two options

[Dan Allen (JIRA)]

split transaction enablement into two options
---------------------------------------------

                 Key: JBSEAM-2022
                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2022
             Project: JBoss Seam
          Issue Type: Feature Request
          Components: Core
    Affects Versions: 2.0.0.CR1
            Reporter: Dan Allen
         Assigned To: Gavin King
            Priority: Minor
             Fix For: 2.0.x


I can see cases where a developer will want to wrap the rendering phase in a transaction, but not the preceding phases. When transaction management is disabled, there are annotations available for wrapping action handler methods in transactions. However, there is no easy way (other than writing a phase listener) to get a transaction wrapped around the render response phase.

I am thinking something like this:

Leave the property transactionManagementEnabled as is.

Add a property restrictTransactionToRenderPhase (or something similarly named)

Interpretation of this property will require a change in SeamPhaseListener

I know that this feels like a bit too much control, but I came across a use case recently where I needed to do several isolated transactions, but since I had the global transaction management enabled, the @Transactional elements on my methods were being ignored (because a global transaction was already in play).

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira