On Wed, Feb 6, 2013 at 6:15 PM, fordm <[email protected]> wrote: > Claus Ibsen-2 wrote >> I think there is a method on CamelTestSupport = >> useOverridePropertiesWithPropertiesComponent you can override and >> return the properties to use for testing. >> I guess we should document that on: >> http://camel.apache.org/camel-test.html. > > There is indeed a useOverridePropertiesWithPropertiesComponent method and > I've tried overriding it but it has no effect. > > The issue appears to be in the CamelBlueprintTestSupport setUp method (a > call to CamelBlueprintHelper.createBundleContext), where the blueprint being > loaded / parsed. Any components (e.g. direct, file, smtp, etc.) seem to be > identified and their resolvers (eagerly?) loaded. It's at this point that > it's trying to find a component resolver for {{email.protocol}}. > > This occurs directly before the useOverridePropertiesWithPropertiesComponent > method call. >
Hi Thanks for sharing your observation. I have logged a ticket https://issues.apache.org/jira/browse/CAMEL-6044 > > > -- > View this message in context: > http://camel.465427.n5.nabble.com/Mocking-an-endpoint-in-a-blueprint-that-contains-a-property-placeholder-tp5726972p5727046.html > Sent from the Camel - Users mailing list archive at Nabble.com. -- Claus Ibsen ----------------- Red Hat, Inc. FuseSource is now part of Red Hat Email: [email protected] Web: http://fusesource.com Twitter: davsclaus Blog: http://davsclaus.com Author of Camel in Action: http://www.manning.com/ibsen
