Hi JB,

My use case is I have a property file inside etc/myAppDir/myConfig.properties 
and I have not registered any ManagedService.class in my bundle. In this case 
can I use blueprint-cm ?

Basically I should be able to explicitly point to the property file and do the 
configuration in my blueprint xml.

Regards
 Jens
-----Original Message-----
From: Jean-Baptiste Onofré [mailto:[email protected]]
Sent: 12 August 2014 13:57
To: [email protected]
Subject: Re: Blueprint PropertyPlaceHolder Support

Hi Jens,

blueprint cm provides a property-placeholder. The persistent-id will be use 
with ConfigAdmin, but you can use straight forward:

<cm:property-placeholder id="myblueprint.placeholder" persistent-id="foo">
   <cm:default-properties>
     <cm:property name="foo" value="bar"/>
   </cm:default-properties>
</cm:property-placeholder>

blueprint ext allows you to load system variable as property, that you can use 
with blueprint:cm:

<ext:property-placeholder placeholder-prefix="$[" placeholder-suffix="]" /> 
<cm:property-placeholder id="myblueprint.placeholder" persistent-id="foo">
   <cm:default-properties>
     <cm:property name="foo" value="$[karaf.base]/my"/>
   </cm:default-properties>
</cm:property-placeholder>

Is it not what you are looking for ?

Regards
JB

On 08/12/2014 10:18 AM, Jens J Parappallil wrote:
> Hi,
>
> I am looking for a simple PropertyPlaceHolder support for blueprint
> xml configuration. As of my knowledge blueprint-cm ties you with the
> ConfigAdmin which I don`t want and
>
> blueprint-ext is limited to osgi properties. Are there any other
> options other than these something similar to the Spring property
> placeholder where we can specify the property file(s), optional resources etc.
>
> Regards
>
> Jens
>
>
>
> DISCLAIMER: "The information in this e-mail and any attachment is
> intended only for the person to whom it is addressed and may contain
> confidential and/or privileged material. If you have received this
> e-mail in error, kindly contact the sender and destroy all copies of
> the original communication. IBS makes no warranty, express or implied,
> nor guarantees the accuracy, adequacy or completeness of the
> information contained in this email or any attachment and is not
> liable for any errors, defects, omissions, viruses or for resultant
> loss or damage, if any, direct or indirect."

--
Jean-Baptiste Onofré
[email protected]
http://blog.nanthrax.net
Talend - http://www.talend.com


DISCLAIMER: "The information in this e-mail and any attachment is intended only 
for the person to whom it is addressed and may contain confidential and/or 
privileged material. If you have received this e-mail in error, kindly contact 
the sender and destroy all copies of the original communication. IBS makes no 
warranty, express or implied, nor guarantees the accuracy, adequacy or 
completeness of the information contained in this email or any attachment and 
is not liable for any errors, defects, omissions, viruses or for resultant loss 
or damage, if any, direct or indirect."

Reply via email to