To use system properties in Blueprint, you should use blueprint-ext.
Do you know how can I combine that with getting other properties from a properties file on the classpath to be used in a camel context?
The following works without the ext:property-placeholder but not combined with it - it fails to find the camelProperty property (defined in some.properties file). Trying to use classpath: prefix in location tag of ext:property-placeholder does not work either.
Any ideas much appreciated.
Edited by: jasonnh on Aug 10, 2012 11:24 AM
My original question has been answered - thanks again.
In case this can help someone I think the problem I am having with mixing property placeholders is a bug that is fixed in camel 2.10.0 (undocumented in the release notes), i.e.:
BlueprintPropertiesPlaceholder.parseProperty method has changed. Basically, 2.9.0 uses a parameter called 'value' as a local variable which gets set to null and then passes that to delegate.parseProperty as if it was unchanged. 2.10.0 declares a separate local variable 'answer' and then passes the orignal 'value' to delegate.parseProperty.