tomee-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Thibaut Robert (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (OPENEJB-1527) JtaEntityManager: wrong delegating call, wrong transaction management
Date Wed, 20 Apr 2011 11:33:05 GMT

     [ https://issues.apache.org/jira/browse/OPENEJB-1527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Thibaut Robert updated OPENEJB-1527:
------------------------------------

    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.

  was:
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.

        Summary: JtaEntityManager: wrong delegating call, wrong transaction management  (was:
JtaEntityManager: wonrg delegating call, wrong transaction management)

> JtaEntityManager: wrong delegating call, wrong transaction management
> ---------------------------------------------------------------------
>
>                 Key: OPENEJB-1527
>                 URL: https://issues.apache.org/jira/browse/OPENEJB-1527
>             Project: OpenEJB
>          Issue Type: Bug
>          Components: cmp2
>    Affects Versions: (trunk/openejb3), 3.2
>            Reporter: Thibaut Robert
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message