You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/07/09 08:26:04 UTC

[jira] [Resolved] (CAMEL-8885) ConsumeLockEntity without ConsumeDelete

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

Claus Ibsen resolved CAMEL-8885.
--------------------------------
       Resolution: Fixed
         Assignee: Claus Ibsen
    Fix Version/s: 2.15.3
                   2.16.0

Thanks for reporting.

> ConsumeLockEntity without ConsumeDelete
> ---------------------------------------
>
>                 Key: CAMEL-8885
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8885
>             Project: Camel
>          Issue Type: Bug
>          Components: camel-jpa
>    Affects Versions: 2.15.2
>            Reporter: Daniel Kowalewski
>            Assignee: Claus Ibsen
>             Fix For: 2.16.0, 2.15.3
>
>
> I think that condition at the beginning of the lock function is wrong:
> {code}
> protected boolean lockEntity(Object entity, EntityManager entityManager) {
>         if (!getEndpoint().isConsumeDelete() || !getEndpoint().isConsumeLockEntity()) {
>             return true;
>         }
> ...
> {code}
> If I wanna just select and then update entity I should set consumeDelete=false, but If so entity will  newer be locked...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)