Re: Blueprint System Properties not resolved

To clarify, I found was is causing the problem, but I don’t have a solution. I need to be able to use Quartz endpoints in Blueprint Camel routes, and at the same time, I need place holder substitution of System properties in the same Blueprint context. Somehow you can’t have both. Best

Re: Blueprint System Properties not resolved

OK, I found what breaks it! When I add this Camel route in a separate Blueprint XML in the same directory: http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:camel="http://camel.apache.org/schema/blueprint;

Re: Blueprint System Properties not resolved

Something interesting happened. When preparing an isolated blueprint.xml to post it here, I removed a lot of other stuff I had, reducing the XML to a bare minimum, and it now works! So, something else in the XML is conflicting, I don’t know what, but I will now add things one at a time, until

Re: Blueprint System Properties not resolved

Do you use both cm and ext namespaces or only ext ? Can you share your blueprint.xml ? Thanks, Regards JB On 09/02/2016 03:21 PM, Alex Soto wrote: Same issue if run as standalone, I even tested adding a cfg file with the configuration entry, but the bundle fails to start and the value in

Re: Blueprint System Properties not resolved

Same issue if run as standalone, I even tested adding a cfg file with the configuration entry, but the bundle fails to start and the value in the configuration file does not seem to be honored. Best regards, Alex soto > On Sep 2, 2016, at 8:59 AM, Jean-Baptiste Onofré

Re: Blueprint System Properties not resolved

Do you have the issue only in Pax Exam or in Karaf standalone container as well ? I just tried with a simple blueprint and it works fine with ext and cm xmlns. Regards JB On 09/02/2016 02:49 PM, Alex Soto wrote: Hi JB, Yes, I saw that other thread, but it is still not working for me. I

Re: Blueprint System Properties not resolved

Hi JB, Yes, I saw that other thread, but it is still not working for me. I printed the user.home value in the activation method of some other DS component, and is it correctly set to the user home directory. It only does not work when referenced in a Blueprint XML. I don’t know if I have

Re: Blueprint System Properties not resolved

Hi Alex, I answered to another user couple of days ago with the same question (system property in blueprint) and he said it works fine. Can you check the actual value of user.home ? I will try by my side. Regards JB On 09/01/2016 07:45 PM, Alex Soto wrote: Hello, I have a blueprint

Re: Blueprint System Properties not resolved

Still didn’t work. Maybe I am running the wrong version? These are the versions of the jar I see under system/org/apache/aries/blueprint directory of Karaf. org.apache.aries.blueprint.api-1.0.1.jar org.apache.aries.blueprint.cm-1.0.7.jar org.apache.aries.blueprint.core-1.4.5.jar

Re: Blueprint System Properties not resolved

Hello Alex, I did use the same, but in my case I had to update the version of the schemas to. http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.3.0 and http://aries.apache.org/blueprint/xmlns/blueprint-ext/v1.5.0

Re: Blueprint System Properties not resolved

No, I checked. This is still in integration test mode, with Pax-Exam, so the directory does not yet have any cfg files other than Karaf’s own. Best regards, Alex soto > On Sep 1, 2016, at 2:12 PM, Guillaume Nodet wrote: > > Are you sure you don't have this value coming

Re: Blueprint System Properties not resolved

Are you sure you don't have this value coming from the configuration in etc/my.config.id.cfg or something like that ? We had such a pattern in multiple places in Karaf 2.x and it was working fine. 2016-09-01 19:45 GMT+02:00 Alex Soto : > Hello, I have a blueprint bundle

Blueprint System Properties not resolved

Hello, I have a blueprint bundle defined as: http://www.osgi.org/xmlns/blueprint/v1.0.0; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:cm="http://aries.apache.org/blueprint/xmlns/blueprint-cm/v1.1.0;