Re: Camel-Maven-Plugin, Felix.Connect, and configAdminFileName

[Ryan Colwell]

I spent some time trying to track this down between Camel 2.15.2 and Camel
2.18. I believe it is a bug/side effect of the fix for CAMEL-9313. I created
a bug with the findings for my analysis here: CAMEL-10476.



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Maven-Plugin-Felix-Connect-and-configAdminFileName-tp5789878p5790109.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel-Maven-Plugin, Felix.Connect, and configAdminFileName

[Ryan Colwell]

Grzegorz -- I did find your post in my travels. Thank you for putting it
together it is very informative and helpful.

In this example:
  

  
  
  
  
  

  

Do you just typically set your defaults to your local settings and skip
providing it via a file? I think referencing content out of "src/test" is
probably safe as that content likely wouldn't be present in a production
bundle. I'm a little concerned about baking development tier configurations
in as defaults. I'm curious how others handle the separation of deploying
code and configuration.

I also found this example today:
https://github.com/cschneider/Karaf-Tutorial/tree/master/camel/order/src
which it looks like the author would use the blueprint propertyplaceholders
for production/karaf but then runs the app with exec:java and loads the
properties with properties component instead of camel:run for local
development. Is this common? Is camel:run considered an anti-pattern at all
for local development? 

Thanks,
Ryan Colwell



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Maven-Plugin-Felix-Connect-and-configAdminFileName-tp5789878p5789976.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Re: Camel-Maven-Plugin, Felix.Connect, and configAdminFileName

[Grzegorz Grzybek]

Hello

I've described how placeholders, camel-test-blueprint and configadmin works
here: http://ggrzybek.blogspot.com/2015/12/camel-blueprint-test-support.html
I hope you'll find something interesting there. If something's confusing,
please let me know.

regards
Grzegorz Grzybek

2016-11-09 22:09 GMT+01:00 Ryan Colwell :

> Is anyone actively using propertyplaceholders with a version of
> camel-test-blueprint later than 2.15.2 from a configuration file for local
> development with camel:run? If so could you describe your setup or link a
> project for reference.
>
> I've started looking through the camel-test-blueprint plugin source and
> have
> been running with debug logging but I haven't yet tracked down where the
> config file seems to get lost.
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.
> com/Camel-Maven-Plugin-Felix-Connect-and-configAdminFileName-
> tp5789878p5789969.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>

Re: Camel-Maven-Plugin, Felix.Connect, and configAdminFileName

[Ryan Colwell]

Is anyone actively using propertyplaceholders with a version of
camel-test-blueprint later than 2.15.2 from a configuration file for local
development with camel:run? If so could you describe your setup or link a
project for reference.

I've started looking through the camel-test-blueprint plugin source and have
been running with debug logging but I haven't yet tracked down where the
config file seems to get lost. 



--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Maven-Plugin-Felix-Connect-and-configAdminFileName-tp5789878p5789969.html
Sent from the Camel - Users mailing list archive at Nabble.com.

Camel-Maven-Plugin, Felix.Connect, and configAdminFileName

[Ryan Colwell]

I've written a few Camel routes in 2.15.2 using blueprint and property
placeholders for configuration values. I'm targeting Karaf as my production
environment and using the Camel-Maven-Plugin for running locally. For my
example I'm using the route generated by (camel-archetype-blueprint) that
logs "The messages contains ${body}" every 5 seconds but I removed the
default value from the property-placeholder.

Blueprint File Snippet(based on camel-archetype-blueprint):
  
  
  
  

Pom:
 
   org.apache.camel
camel-maven-plugin
2.15.2

 com.ds.configstest

config/com.ds.configstest.cfg



config/com.ds.configstest.cfg properties file:
greeting=Hello from config file

The above works great in Camel 2.15.2. When it ran locally or in Karaf(4) it
printed "The message contains Hello from config file." It allowed me to do
local testing with a config file for and then my deployments dropped QA/PROD
specific configs in $KARAF_HOME/etc/com.ds.configstest.cfg.

When I tried with today with a new project from camel-archetype-blueprint
using version 2.18.0 of Camel and I run locally with camel-maven-plugin the
log statement just prints the literal "The message contains ${greeting}" as
if the com.ds.configstest is not being picked up and applied. When I run it
in Karaf(4) it picks up the com.ds.configstest and correctly prints "The
message contains Hello from config file" in the log statement.

Does configAdminFileName work differently with the change from PojoSR to
Felix Connect as discussed in the Running OSGI Blueprint section of this
page? Can you no longer load configs to the registry this way for local
testing? https://camel.apache.org/camel-run-maven-goal.html. 

Thanks,

Ryan




--
View this message in context: 
http://camel.465427.n5.nabble.com/Camel-Maven-Plugin-Felix-Connect-and-configAdminFileName-tp5789878.html
Sent from the Camel - Users mailing list archive at Nabble.com.