On 22 June 2010 12:19, Danushka Menikkumbura <[email protected]> wrote: > Hi Sorin, > > You mean OSGi-ing the broker altogether?. > > Thanks, > Danushka
Yes, I think this would give us a more flexible product that can be used in a variety of places. I don't think it would require much work. - Change our startup to start the felix container. - Give the core broker an activator to kick start its loading as we have now. - Change PluginManager to simply be a helper lookup class. I'd be intereseted to know what the other devs think about the approach, would be good to foster a community of plugins that can augment the broker's functionality. Martin > Hi Danushka, >> At the moment the broker is using Felix to start its plugins and it is >> not itself OSGI pluggable (it starts felix embedded). Yes, it would >> be great to have the broker embeddable in an OSGI provider (eg >> dm-server, equinox, felix in no particular order) and load its >> dependencies (removing the PluginManager and Felix, etc). >> Can we have your oppinion here guys? How should we go about OSGI in java >> broker? >> >> Thanks, >> >> Sorin > > > -- > Danushka Menikkumbura > Apache Axis2 PMC Member > > Apache Qpid - World Domination through Advanced Message Queueing ; > http://qpid.apache.org > > phone : +94 77 364 1754 > personal blog : http://danushka-menikkumbura.blogspot.com/ > <http://danushka-menikkumbura.blogspot.com/>technical blog : > http://danushkastechythoughts.blogspot.com/ > <http://danushkastechythoughts.blogspot.com/>twitter : > http://twitter.com/danushkamenik > <http://twitter.com/danushkamenik>linkedin : > http://lk.linkedin.com/in/danushka > -- Martin Ritchie --------------------------------------------------------------------- Apache Qpid - AMQP Messaging Implementation Project: http://qpid.apache.org Use/Interact: mailto:[email protected]
