[JBoss JIRA] (AS7-2968) @PreUpdate entity callback not running in caller's context when Container Managed Transactions are used
9:30 a.m.
@PreUpdate entity callback not running in caller's context when Container Managed
Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: jaikiran pai
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
9:40 a.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
jaikiran pai reassigned AS7-2968:
---------------------------------
Assignee: Scott Marlow (was: jaikiran pai)
Scott, assigning this to you since you have been discussing this with jw in the forums.
Let me know if this turns out to be some EJB interceptor issue.
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: Scott Marlow
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
9:04 p.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-2968:
------------------------------
Fix Version/s: 7.1.0.CR1
Forum Reference: http://community.jboss.org/thread/175844?tstart=0 (was:
http://community.jboss.org/thread/175844?tstart=0)
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: Scott Marlow
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
6:57 a.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2968:
-----------------------------------
Test case added to https://github.com/scottmarlow/jboss-as/tree/as7-2968. Calling
EntityManager.flush() may be another workaround.
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: Scott Marlow
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
6:59 a.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
Scott Marlow updated AS7-2968:
------------------------------
Workaround Description: Call EntityManager.flush() or use User Transactions instead of
Container Managed Transactions.
Workaround: Workaround Exists
Forum Reference: http://community.jboss.org/thread/175844?tstart=0 (was:
http://community.jboss.org/thread/175844?tstart=0)
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: Scott Marlow
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
10:14 a.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2968:
-----------------------------------
When the test (EntityListenersTestCase) calls cmt.updateEmployee(emp) to update the
entity, as we prepare for the stateful bean call, StatefulComponentInstanceInterceptor
sets ComponentInstance.class in context private data.
When the cmt.updateEmployee() returns, we return up the stack to the
StatefulComponentInstanceInterceptor, which clears ComponentInstance.class in context
private data.
Later up the stack, the TX interceptor commits the transaction. This properly triggers the
database update, however when the user code, calls indirectly to CurrentInvocationContext,
the context has no private data for ComponentInstance.class. So, we throw
currentComponentNotAEjb(component).
I think that the proper fix, is having StatefulComponentInstanceInterceptor, handoff the
clearing of the ComponentInstance.class in context private data to happen after the tx
ends. Maybe we could hand that off to happen at the end of
CMTTxInterceptor.processInvocation().
Is that possible?
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: Scott Marlow
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
10:16 a.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
Scott Marlow reassigned AS7-2968:
---------------------------------
Assignee: jaikiran pai (was: Scott Marlow)
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: jaikiran pai
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
2:24 p.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2968:
-----------------------------------
Jaikiran,
Or could use the TransactionSynchronizationRegistry to clear the context private data
after the tx completion. Let me know if you want me to give this a try (just assign the
jira back). There could be more to it, than I know about.
Scott
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: jaikiran pai
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
8:42 a.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2968:
-----------------------------------
A simpler fix might be to move the setting/clearing of ComponentInstance.class to a
different interceptor.
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: jaikiran pai
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
9:40 a.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
jaikiran pai commented on AS7-2968:
-----------------------------------
Scott, I haven't looked completely into the details of this. But after a quick glance,
I think the instance associating interceptor (StatefulComponentInstanceInterceptor) should
be ordered prior to the transaction interceptor. Could you try changing the following
order in InterceptorOrder class:
{code}
public static final int ASSOCIATING_INTERCEPTOR = 0x700;
{code}
to
{code}
public static final int ASSOCIATING_INTERCEPTOR = 0x440;
{code}
i.e. move it before the tx interceptors.
I haven't looked too much into the other details yet, but I'll take a look
tomorrow. Let me know if this works.
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: jaikiran pai
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
8:23 p.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2968:
-----------------------------------
Jaikiran,
I tried your suggestion and that fixed the issue. The test case and suggested change are
on my [branch|https://github.com/scottmarlow/jboss-as/tree/as7-2968].
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: jaikiran pai
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
7:12 a.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
Scott Marlow commented on AS7-2968:
-----------------------------------
Jaikiran,
No problem at all and thanks for your help! I see that the change was merged and I think
that we can close this.
Perhaps jw can try a [nightly build tomorrow|http://community.jboss.org/thread/167590] to
try the fix.
Scott
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: jaikiran pai
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
3:45 p.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
Jason Greene reopened AS7-2968:
-------------------------------
See pull request comments
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: jaikiran pai
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
4:20 a.m.
[
https://issues.jboss.org/browse/AS7-2968?page=com.atlassian.jira.plugin.s...
]
jw commented on AS7-2968:
-------------------------
Tested on CR1B and it works
@PreUpdate entity callback not running in caller's context when
Container Managed Transactions are used
-------------------------------------------------------------------------------------------------------
Key: AS7-2968
URL: https://issues.jboss.org/browse/AS7-2968
Project: Application Server 7
Issue Type: Bug
Components: EJB, JPA / Hibernate
Affects Versions: 7.1.0.Beta1
Reporter: jw
Assignee: jaikiran pai
Fix For: 7.1.0.CR1
If an Entity Bean has a @PreUpdate listener, the listener is not called in the context of
the caller (session bean) in case of Container Managed Transactions.
As a result, an jndi lookup in the callback for 'java:comp/EJBContext' returns
always null. The @PreUpdate callback should run in the context of the caller.
{noformat}
@Entity
@EntityListeners({ MyListener.class })
public class MyEntity {
...
}
{noformat}
{noformat}
public class MyListener {
@PreUpdate
@PrePersist
public void onEntityCallback(Object entity) {
EJBContext ctx;
ctx = createInitialContext().lookup("java:comp/EJBContext");
System.out.println(ctx.getCallerPrincipal().getName());
}
}
{noformat}
{noformat}
@Stateless
public class MyServiceBean implements MyServiceRemote {
@Override
public void updateEntity(MyEntity entity) {
entityManager.merge(entity);
}
}
{noformat}
This listener works fine on @PrePersist (Container- and Bean Managed Transactions) but
fails on @PreUpdate with a NullPointerException if container managed transactions are
used.
Workaround: use User Transactions instead of Container Managed Transactions
--
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
4667
days inactive
4720
days old
13 comments
8 participants
participants (8)
-
jaikiran pai (Assigned) (JIRA) -
jaikiran pai (Commented) (JIRA)
-
Jason Greene (Reopened) (JIRA)
-
jw (Created) (JIRA)
-
jw (JIRA)
-
Scott Marlow (Assigned) (JIRA)
-
Scott Marlow (Commented) (JIRA)
-
Scott Marlow (Updated) (JIRA)