[jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-369) @Create and @Begin(FlushModeType.MANUAL) execute in wrong order

[Gavin King (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBSEAM-369?page=all ]

Gavin King closed JBSEAM-369.
-----------------------------

    Fix Version/s: 1.1.0.BETA2
                       (was: 1.1.0.CR1)
       Resolution: Done

That makes perfect sense, since @Begin has its effect AFTER the end of the method call. You will see the same thing if you print out Managed.isLongRunningConversation(). Closing.

> @Create and @Begin(FlushModeType.MANUAL) execute in wrong order
> ---------------------------------------------------------------
>
>                 Key: JBSEAM-369
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-369
>             Project: JBoss Seam
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 1.1.0.BETA2
>            Reporter: Christian Bauer
>         Assigned To: Gavin King
>            Priority: Minor
>             Fix For: 1.1.0.BETA2
>
>
> This is CVS HEAD:
> @Name("catalog")
> @Stateful
> public class CatalogBean implements Catalog {
>     @In(value = "caveatEmptorEM", create = true)
>     private EntityManager em;
>     @Create
>     @Begin(flushMode = FlushModeType.MANUAL)
>     public void refreshRootCategories() {
>     ...
> }
> The EntityManager is in FlushMode.AUTO because it is injected before the ConversationInterceptor runs and reads the @Begin annotation. 
> So ManagedPersistenceContext.create() runs and sets the flush mode before the setFlushMode() method on the Conversation component is called.

-- 
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