I'm currently using iPOJO to publish OSGi services. The main reason why I'm
using iPOJO (instead of blueprint) is that I can easily disable/enable my
services by using iPOJO's @Controller annotation. To enable my service I
just change a configuration property to false and to enable it I set it to
true again.

I would like to use blueprint instead. Mainly because:

a) Blueprint comes out-of-the-box with Apache Karaf
b) Blueprint feels more like a standard
c) Blueprint does not require any manipulation

Is there a way to achieve the same functionality with blueprint (to
enble/disable services using a configuration property)?

/Bengt

Reply via email to