[
https://issues.apache.org/jira/browse/CAMEL-7372?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13971382#comment-13971382
]
ASF GitHub Bot commented on CAMEL-7372:
---------------------------------------
GitHub user igarashitm opened a pull request:
https://github.com/apache/camel/pull/136
CAMEL-7372 Allow users to pass in their own EntityManager through the ex...
...change
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/igarashitm/camel CAMEL-7372
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/camel/pull/136.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #136
----
commit c4e25aa350c264f202c71401c32e0829141e2631
Author: Tomohisa Igarashi <[email protected]>
Date: 2014-04-16T13:04:02Z
CAMEL-7372 Allow users to pass in their own EntityManager through the
exchange
----
> Allow users to pass in their own EntityManager through the exchange
> -------------------------------------------------------------------
>
> Key: CAMEL-7372
> URL: https://issues.apache.org/jira/browse/CAMEL-7372
> Project: Camel
> Issue Type: Improvement
> Components: camel-jpa
> Reporter: igarashitm
>
> Currently JpaProducer always creates its own EntityManager instance, but then
> if user application also creates EntityManager or receives container-managed
> one, each EntityManager instance has its own 1st level cache. It's nice to
> have JpaProducer to accept EntityManager instance from outside via message
> header so user application can pass it in.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
