[
https://issues.jboss.org/browse/WFLY-6127?page=com.atlassian.jira.plugin....
]
kostd kostd commented on WFLY-6127:
-----------------------------------
[~smarlow], can you accept [~veselroger] `s commit (which adds the jboss.as.jpa.syncasjoin
option and "relaxed" check against current.isJoined instead of
current.getSyncType() == Synchronized)? JCP process seems stopped
(
https://javaee-guardians.io/lack-of-java-ee-8-progress/) and our feedback to Linda is too
late :(
What we can do to you able to accept? may be some ut or something like that?
We can rework to take your comments.
Throw IllegalStateException if JTA tx has an unsynchronized
persistence context and the target is synchronized persistence context
----------------------------------------------------------------------------------------------------------------------------------
Key: WFLY-6127
URL:
https://issues.jboss.org/browse/WFLY-6127
Project: WildFly
Issue Type: Bug
Components: JPA / Hibernate
Affects Versions: 9.0.2.Final
Reporter: Mazen Mahmoud
Assignee: Scott Marlow
Priority: Blocker
Fix For: 10.1.0.CR1, 10.1.0.Final
Attachments: server-log.txt
SPEC: If a component is called and the JTA transaction is propagated into that
component:
If there is a persistence context of type SynchronizationType.UNSYNCHRONIZED
associated with the JTA transaction and the target component specifies a persistence
context of type SynchronizationType.SYNCHRONIZED, the IllegalStateException is thrown by
the container
We have a stateful session bean (SFB1) / PC: TRANSACTION/UNSYNCHRONIZED)
stateful session bean (SFB2) / PC: TRANSACTION/SYNCHRONIZED)
SFB1 method M1 (REQUIRED) calls SFB2 Method 2 (REQUIRED):
PC is propagated from SFB1 to SFB2 without any exception.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)