Return-Path: X-Original-To: apmail-aries-dev-archive@www.apache.org Delivered-To: apmail-aries-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2F71218ACA for ; Thu, 23 Jul 2015 14:33:05 +0000 (UTC) Received: (qmail 19133 invoked by uid 500); 23 Jul 2015 14:33:05 -0000 Delivered-To: apmail-aries-dev-archive@aries.apache.org Received: (qmail 19086 invoked by uid 500); 23 Jul 2015 14:33:04 -0000 Mailing-List: contact dev-help@aries.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@aries.apache.org Delivered-To: mailing list dev@aries.apache.org Received: (qmail 19069 invoked by uid 99); 23 Jul 2015 14:33:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 23 Jul 2015 14:33:04 +0000 Date: Thu, 23 Jul 2015 14:33:04 +0000 (UTC) From: "Matt Pavlovich (JIRA)" To: dev@aries.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (ARIES-1355) blueprint-jpa does not interpolate configuration properties MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/ARIES-1355?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14638909#comment-14638909 ] Matt Pavlovich commented on ARIES-1355: --------------------------------------- Christian- Thanks for the quick response. The driving factor to allow for multiple persistence units is to readily support variances between DB vendors. Having it be configurable provides even greater flexibility (no need to have separate modules). Off the top of my head, I don't see how an annotation would be able to support that scenario. Are there other factors driving the move away from the blueprint-defined jpa:unit/context? I'm not tied to any particular solution, but having configurable PU's would be a very useful capability. Thanks > blueprint-jpa does not interpolate configuration properties > ----------------------------------------------------------- > > Key: ARIES-1355 > URL: https://issues.apache.org/jira/browse/ARIES-1355 > Project: Aries > Issue Type: Bug > Components: Blueprint > Affects Versions: blueprint-cm-1.0.6 > Reporter: Matt Pavlovich > > When attempting to wire in the persistent unit name from a cm property, aries jpa does not interpolate the value, and instead tries to lookup the ${name} literally. > {noformat} > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:camel="http://camel.apache.org/schema/blueprint" > xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.0.0" > xmlns:jpa="http://aries.apache.org/xmlns/jpa/v1.1.0" xmlns:tx="http://aries.apache.org/xmlns/transactions/v1.1.0" > xsi:schemaLocation=" > http://www.osgi.org/xmlns/blueprint/v1.0.0 http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd"> > > > > > > > > > .. > {noformat} > Log message > {noformat} > [(&(&(!(org.apache.aries.jpa.proxy.factory=*))(osgi.unit.name=${persistentUnitName}))(objectClass=javax.persistence.EntityManagerFactory)), (&(&(!(org.apache.aries.jpa.proxy.factory=*))(osgi.unit.name=${persistentUnitName}))(objectClass=javax.persistence.EntityManagerFactory))] > java.util.concurrent.TimeoutException > {noformat} -- This message was sent by Atlassian JIRA (v6.3.4#6332)