[jboss-jira] [JBoss JIRA] (WFLY-7156) UNSYNCHRONIZED extended persistence context associated but not joined with JTA transaction and target component is persistence context of SYNCHRONIZED, IllegalStateException should be thrown

[Scott Marlow (JIRA)]

Scott Marlow created WFLY-7156:
----------------------------------

             Summary: UNSYNCHRONIZED extended persistence context associated but not joined with JTA transaction and target component  is persistence context of SYNCHRONIZED, IllegalStateException should be thrown
                 Key: WFLY-7156
                 URL: https://issues.jboss.org/browse/WFLY-7156
             Project: WildFly
          Issue Type: Feature Request
          Components: JPA / Hibernate
    Affects Versions: 10.1.0.Final
         Environment: *AppServer:* WildFly 10.1.0.Final
*WildFly-jpa:* wildfly-jpa-10.1.0.Final.jar
            Reporter: Scott Marlow
            Assignee: Scott Marlow
             Fix For: 11.0.0.Alpha1


As we mentioned in https://issues.jboss.org/browse/WFLY-6127 we found bug and made our solution.
 
*The obtained defect:*
A defect related to the check of synchronization type (to satisfy JPA spec 2.1 section 7.6.4.1) was found in WildFly 10.1.0.Final.
The Method getSynchronizationType of class ExtendedEntityManager ALWAYS returns type of synchronization as SYNCHRONIZED (jar file: wildfly-jpa-10.1.0.Final.jar)

*FIX:*
We made a fork of WildFly-jpa project at: https://github.com/argustelecom/wildfly/tree/WFLY-6127
Our Fix commit: https://github.com/wildfly/wildfly/commit/3bff5fde3cfc23f3999dc75c320029e69c562c40
_Changes_: The method getSynchronizationType returns declared synchronization type. 




--
This message was sent by Atlassian JIRA
(v6.4.11#64026)