Return-Path: X-Original-To: apmail-camel-issues-archive@minotaur.apache.org Delivered-To: apmail-camel-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 75BCB11191 for ; Wed, 16 Apr 2014 14:04:23 +0000 (UTC) Received: (qmail 95960 invoked by uid 500); 16 Apr 2014 13:04:22 -0000 Delivered-To: apmail-camel-issues-archive@camel.apache.org Received: (qmail 95898 invoked by uid 500); 16 Apr 2014 13:04:18 -0000 Mailing-List: contact issues-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list issues@camel.apache.org Received: (qmail 95883 invoked by uid 99); 16 Apr 2014 13:04:14 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 16 Apr 2014 13:04:14 +0000 Date: Wed, 16 Apr 2014 13:04:14 +0000 (UTC) From: "igarashitm (JIRA)" To: issues@camel.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (CAMEL-7372) Allow users to pass in their own EntityManager through the exchange MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 igarashitm created CAMEL-7372: --------------------------------- Summary: 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)