When I go through the code what I see is that the use of OSGi framework here is more of a service repository but nothing else (correct me if I am wrong). In other words it a reflection interface. I don't think it even enables updating a bundle without restarting the VM. If that is the case, I suggest we get rid of this altogether and have a simple plugin repository. Once that is done, bundle-ifying Qpid will not be too tedious a task, there are some issues like including Qpid-specific classes inside 3rd-party packages as I have mentioned in another thread, though. We can look into completely OSGi-fying Qpid in the mean time.
Danushka On Wed, Jun 23, 2010 at 2:31 PM, Paul Fremantle <[email protected]> wrote: > My first thoughts are that we should be using Felix in an OSGi > compliant way: not calling felix specifically. > > My second thoughts are that it ought to be easy to at least bundle-ify > the QPid jars so that they fit into an OSGi model. > > The third aspect: completely OSGi-fying QPid - seems like maybe more > work and more of a requirement on users. I'd love it, but I think that > could be put in place later maybe? Of course if its really easy, then > that's even better. > -- 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
