I've always had problems with using cfg files in CBTS and don't know exactly why. I think it may be a loading life cycle issue. For example, in using CXF I'll commonly specify the service class in the configuration file. What I'v resorted to doing is using multiple blueprint files. Blueprint for blueprint-properties.xml that has nothing but the property definition block with PID and defaults, the camel-blueprint.xml that shows sets up the camel context, etc. At test time I'll point to the src/test/resources/test-blueprint-properties.xml instead of the blueprint.xml and it works fine.
On Fri, Feb 19, 2016 at 5:28 AM, Ephemeris Lappis < [email protected]> wrote: > Hello again. > > I've build a simple project with simple routes to test the property > restitution (the ZIP is attached). The blueprint and its configuration file > work as expected deployed on my ServiceMix 6.1.0 that comes with Camel > 2.16.1 as my unit tests. > > The file "error-2_16_1.txt" is a copy of the console when the unit test is > running with Camel 2.16.1. > > The file "error-2_14_0.txt" is the exception that is thrown by JUnit with > Camel 2.14.0, that seems to work worst for property resolution : properties > that are found inside Camel routes like te logger name with 2.16.1 are not > with the 2.14.0. > > I hope this can help you to find an idea... > > Thanks again. > > Regards. > > error-2_16_1.txt > <http://camel.465427.n5.nabble.com/file/n5777913/error-2_16_1.txt> > error-2_14_0.txt > <http://camel.465427.n5.nabble.com/file/n5777913/error-2_14_0.txt> > camel-bp-test.zip > <http://camel.465427.n5.nabble.com/file/n5777913/camel-bp-test.zip> > > > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/cxf-bean-doesn-t-resolve-properties-with-CamelBlueprintTestSupport-tp5777834p5777913.html > Sent from the Camel - Users mailing list archive at Nabble.com. >
