Willem,
I did add: <reference id="vmProperties" interface="java.util.Properties"/>
However it cannot resolve the property. It is as if it can find the service
yet the properties are not there.
Caused by: java.lang.IllegalArgumentException: Property with key
[customer.event.endpoint] not found in properties from text:
{{customer.event.endpoint}}
Claus, yes I am using two separate bundles.
In my Java/Blueprint solution I put something like this:
<reference id="vmProperties" interface="java.util.Properties"/>
<bean id="myRoute" class="com.myapp.MyRoute">
<property name="props" ref="vmProperties"/>
</bean>
MyRoute extends RouteBuilder and has a class member named props.
private Properties props;
public Properties getProps() {
return props;
}
public void setProps(Properties props) {
this.props = props;
}
I then have some code logic and this solution works as I mentioned in my
first post. I can use that but wanted to see if the communal genius knew of
a better way. What solutions are out there for shared properties so that the
only related bundles need restart? I'm looking for granularity of control.
--
View this message in context:
http://camel.465427.n5.nabble.com/Reference-OSGI-Blueprint-java-util-Properties-service-in-Blueprint-Camel-property-placeholder-tp5726985p5727538.html
Sent from the Camel - Users mailing list archive at Nabble.com.
