[jboss-jira] [JBoss JIRA] (WFLY-3105) Container-managed EXTENDED persistence context is always joined with transaction even if UNSYNCHRONIZED

[Christian Bauer (JIRA)]

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

Christian Bauer commented on WFLY-3105:
---------------------------------------

Of course there is this in JPA 2.1 section 7.6.3: "The association of the extended persistence context with the JTA transaction is independent of the synchronization type of the persistence context and whether the persistence context has been joined to the transaction."

What does that even mean?
                
> Container-managed EXTENDED persistence context is always joined with transaction even if UNSYNCHRONIZED
> -------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-3105
>                 URL: https://issues.jboss.org/browse/WFLY-3105
>             Project: WildFly
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>          Components: JPA / Hibernate
>    Affects Versions: 8.0.0.Final
>            Reporter: Christian Bauer
>            Assignee: Scott Marlow
>
> https://github.com/weld/wildfly/blob/master/testsuite/integration/basic/src/test/java/org/jboss/as/test/integration/jpa/transaction/UnsynchronizedSFSB.jav
> Change this test to {code}@PersistenceContext(type = EXTENDED, synchronization = UNSYNCHRONIZED){code} and it will break. 
> Looks like an extended PC is always joined to the transaction and flushed on commit, the unsynchronized mode is ignored. From what I can see this is not specified and indeed would make the whole new UNSYNCHRONIZED feature kind of pointless. It's primary use case is propagation of unflushed/unsynchronized extended PC from a SFSB to other beans while keeping transactions intact.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira