[OPENEJB-1527] JtaEntityManager: wrong delegating call, wrong transaction management

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.2, 4.7.0
• Fix Version/s: 3.2, 4.0-beta-1, 4.0
• Component/s: cmp2
• Assignee: Thibaut Robert
• Reporter: Thibaut Robert
• Created: 20/Apr/11 11:30
• Updated: 02/Jun/14 20:01
• Resolved: 20/Apr/11 16:34

Description

There are issues in JPA 2.0 methods:

• In the following methods:
  public void lock(Object entity, LockModeType lockMode, Map<String, Object>
  properties) {
  public void refresh(Object entity, LockModeType lockMode, Map<String,
  Object> properties) {
  public void refresh(Object entity, LockModeType lockMode) {
  public void refresh(Object entity, Map<String, Object> properties) {
  entityManager is used in place of entity in the delegating call.

• Transaction management is not always correct (or at least not consistent
  with JPA1 methods)
  e.g. refresh methods does not assume an active transaction.

• Less important, timing measurement is implemented JPA 1 methods but not JPA2.