camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Christian Mueller (JIRA)" <>
Subject [jira] Commented: (CAMEL-2980) camel-jpa doesn't use EntityManager.merge(entity) in the right way
Date Mon, 26 Jul 2010 21:52:52 GMT


Christian Mueller commented on CAMEL-2980:

The Camel JPA [wiki page|] explains, that: "_The body of the
In message is assumed to be an entity bean (that is, a POJO with an @Entity annotation on
I wonder, whether the wiki page is outdated (because the code looks like that we support also
collections, ... as body). To be sure, first I will write some unit tests for this...


> camel-jpa doesn't use EntityManager.merge(entity) in the right way
> ------------------------------------------------------------------
>                 Key: CAMEL-2980
>                 URL:
>             Project: Apache Camel
>          Issue Type: Bug
>          Components: camel-jpa
>    Affects Versions: 2.4.0
>         Environment: All
>            Reporter: Christian Mueller
>            Assignee: Christian Mueller
>             Fix For: 2.5.0
> The EntityManager.merge(entity) method returns the merged entity. The exchange in message
body should be updated with the merged entity (what camel-jpa currently not do).
> I running into this problem, because after saving an entity in the database, the id field
was still null. So, we don't know, which entity in the database is the corresponding to this
entity... :-(
> Have a look in the process method of [JpaProducer|]
and the Java doc from the [EntityManager|].
> Christian

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message