Hi Dejan, thank you for details.
As I see, activemq-osgi contains all functionality (client, broker, all transports, dependencies etc.). I'd like to use only small functionality sub-scope (e.g. client + http transport). With previous versions, I can use bundles/modules I need. With the latest version, I have to include all functionality into my osgi framework and I don't have any way to configure it. Of course, I can wrap the other activemq jars and add osgi manifest headers on the fly, but it's not "off the shelf" solution. Or did I miss something? -- Best regards, Dmytro Pishchukhin On Tue, Feb 12, 2013 at 2:46 PM, Dejan Bosanac <[email protected]> wrote: > Hi Dmytro, > > we changed the modules of the activemq for 5.8.0 and how it integrates > with osgi containers. You can find more details on it here > > http://activemq.apache.org/osgi-integration.html > > but in a nutshell, there's now activemq-osgi bundle that incorporates > all classes and is ready to be used in osgi land. You can also take a > look at karat features for 5.8.0 and see how it's deployed. > > > Regards > -- > Dejan Bosanac > ---------------------- > Red Hat, Inc. > FuseSource is now part of Red Hat > [email protected] > Twitter: @dejanb > Blog: http://sensatic.net > ActiveMQ in Action: http://www.manning.com/snyder/ > > > On Tue, Feb 12, 2013 at 2:41 PM, Dmytro Pishchukhin > <[email protected]> wrote: >> Hi, >> >> I've just found that ActiveMQ 5.8.0 artifacts do no contain OSGi >> headers in manifest files. What was the reason to remove them? >> >> Thanks in advance. >> >> -- >> Best regards, >> Dmytro Pishchukhin
