Defining the connection factory in a separate blueprint file works. If it is not possible to access the osgi namespace inside the activemq.xml file, how can I read properties from the osgi configuration admin service, since this is the way to configure modules in apache karaf?
It's still necessary to include osgi support in the activemq-broker configuration files! Are there any attempts to support it? Should I submit a bug report? -- View this message in context: http://activemq.2283324.n4.nabble.com/activemq-broker-and-osgi-service-registry-tp4674205p4674542.html Sent from the ActiveMQ - User mailing list archive at Nabble.com.
