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 93AA218084 for ; Mon, 27 Jul 2015 23:31:17 +0000 (UTC) Received: (qmail 40139 invoked by uid 500); 27 Jul 2015 23:31:04 -0000 Delivered-To: apmail-aries-dev-archive@aries.apache.org Received: (qmail 40091 invoked by uid 500); 27 Jul 2015 23:31: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 40077 invoked by uid 99); 27 Jul 2015 23:31:04 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jul 2015 23:31:04 +0000 Date: Mon, 27 Jul 2015 23:31: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=14643609#comment-14643609 ] Matt Pavlovich commented on ARIES-1355: --------------------------------------- Giuseppe: That isn't a real viable option, b/c then the code needs to handle all possible combinations of vendor + jta/non-jta mysql, mysql+jta, mssql, mssql+jta, h2sql, etc Is there another reason to EOL the blueprint jpa support and not support config interpolation? > 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)