That would be great :-)
As Reza says, now we have @Transactional proposed for the platform, this scope makes a lot
more sense.
On 15 Feb 2012, at 08:26, Rick Hightower wrote:
I believe at one point I sent out a proposal. I can dig through my
notes. It was shot full of holes and then I thought it was decided that we were not going
to proceed on this. To be honest, I don't recall the details, but I can look it up.
On Tue, Feb 14, 2012 at 7:03 PM, George Gastaldi (JIRA)
<jira-events(a)lists.jboss.org> wrote:
[
https://issues.jboss.org/browse/CDI-121?page=com.atlassian.jira.plugin.sy...
]
George Gastaldi commented on CDI-121:
-------------------------------------
+1 to previous comment.
> TransactionScope
> ----------------
>
> Key: CDI-121
> URL:
https://issues.jboss.org/browse/CDI-121
> Project: CDI Specification Issues
> Issue Type: Feature Request
> Components: Contexts
> Environment: Java EE
> Reporter: Richard Hightower
> Assignee: Richard Hightower
> Priority: Minor
> Fix For: 1.1 (Proposed)
>
> Original Estimate: 3 days
> Remaining Estimate: 3 days
>
> Add TransctionalScope as a standard scope to define beans whose lifecycle is the
same as a given transaction.
> This scope should start automatically when a transaction starts (but lazily when
actually needed).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev
--
Rick Hightower
(415) 968-9037
Profile
_______________________________________________
cdi-dev mailing list
cdi-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/cdi-dev