Return-Path: Delivered-To: apmail-qpid-dev-archive@www.apache.org Received: (qmail 53625 invoked from network); 2 Jul 2010 13:38:35 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 2 Jul 2010 13:38:35 -0000 Received: (qmail 20662 invoked by uid 500); 2 Jul 2010 13:38:35 -0000 Delivered-To: apmail-qpid-dev-archive@qpid.apache.org Received: (qmail 20471 invoked by uid 500); 2 Jul 2010 13:38:33 -0000 Mailing-List: contact dev-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@qpid.apache.org Delivered-To: mailing list dev@qpid.apache.org Received: (qmail 20463 invoked by uid 99); 2 Jul 2010 13:38:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jul 2010 13:38:31 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FREEMAIL_FROM,HTML_MESSAGE,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of danushka.menikkumbura@gmail.com designates 209.85.214.170 as permitted sender) Received: from [209.85.214.170] (HELO mail-iw0-f170.google.com) (209.85.214.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Jul 2010 13:38:26 +0000 Received: by iwn36 with SMTP id 36so2771710iwn.15 for ; Fri, 02 Jul 2010 06:38:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:mime-version:received:in-reply-to :references:from:date:message-id:subject:to:content-type; bh=iOIaLHIxZLv7U6yDX1CmsujJQFJ03AzqdcmOsqtdO4I=; b=lkZelNublOnMp/7CORDuKE9cQSAsGxUok1afRiomcv20TZfp1fVSi3ObTBRD21pgmn cRDgaKKyBAfIwikrEyB/zHtrMjFU3y9yaLsVRrgOMrag0RsGELIpt3wDKT1b/M4KgQD7 Lk1ez9EkNuJiTUZTXSEC1a9XJmTeV2a7CUs4Y= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; b=uvsHqzeTapzaPxkmrYL356PssZqAr/rpCtzwp5SPnAzvtPiYDuvbz8t0IsXstLFuao iRiJ5t3tck234kRvUObWPhdpjqHhvkeFg8bR9Ps/tC0ToBIx/qK7JAhNGyz6qbfH5ney 3Uii4rHnCZf0yfmne3PuD25bA4KWK7MzILHWM= Received: by 10.231.32.134 with SMTP id c6mr835574ibd.156.1278077877206; Fri, 02 Jul 2010 06:37:57 -0700 (PDT) MIME-Version: 1.0 Received: by 10.231.20.73 with HTTP; Fri, 2 Jul 2010 06:37:37 -0700 (PDT) In-Reply-To: References: From: Danushka Menikkumbura Date: Fri, 2 Jul 2010 19:07:37 +0530 Message-ID: Subject: Re: QPID-2705: New Plug-in Architecture for the Java Broker To: dev@qpid.apache.org Content-Type: multipart/alternative; boundary=002215048e77ddbe3f048a67b144 X-Virus-Checked: Checked by ClamAV on apache.org --002215048e77ddbe3f048a67b144 Content-Type: text/plain; charset=ISO-8859-1 Hi Marnie, My immediate approach was to have a new plug-in management mechanism as I could see that it was not possible to have Felix running inside Equinox. I am having a deeper look at whats going wrong here. I will keep this thread updated. Even though my non-OSGi plug-in manager runs fine in my application, not tested for all possible scenarios, though. Thanks, Danushka On Fri, Jul 2, 2010 at 6:52 PM, Marnie McCormack < marnie.mccormack@googlemail.com> wrote: > Hi Danuska, > > What would be really helpful here would be to get stack trace/logs/details > on what happens when you tried to use Felix inside Equinox ? Its not > currently clear why this doesn't work so hard to comment on what we need to > do next. > > Currently the plugin manager uses Felix as a registry of factories, rather > than write our own factory manager. Felix also handles dependency resolver > and the manifest for the plug-ins. > > If we can help you get Felix running I think that'd might be the best way > to > go ? > > There's definitely some refactoring required on the plug in interfaces > though. > > Regards, > Marnie > > On Wed, Jun 30, 2010 at 11:19 AM, Danushka Menikkumbura < > danushka.menikkumbura@gmail.com> wrote: > > > Hi Andrew, > > > > I spent fair amount of time looking at how to hookup one OSGi runtime > with > > another but could not find anything. I am more than happy if that is > > possible because I am doing something that I am not intended to do. > Please > > let me know if you think there is a better approach. > > > > Thanks, > > Danushka > > > > Hi Danushka, > > > > > > I think I agree with Sorin here. I don't think we gain anything by > > > moving away from the OSGi plugin architecture we have now - it has > > > been in place for a long time, and works well. As far as I can see, we > > > would just end up rewriting much of the functionality that Felix > > > provides for us already, which seems like a waste of resources, unless > > > there is another benefir I haven't seen. I agree that *some* further > > > refactoring of the plugin interfaces would be nice - perhaps making > > > them paramaterised by their configuration class, and using generics a > > > little better in the factories and activators, such that we could have > > > a single parent abstract factory, activator and plugin that would be > > > extended. > > > > > > I will comment separately on the issue you raised about re-factoring > > > (QPID-2705), but perhaps if you gave more details on the issue you > > > mentioned in your message of 22 June 2010 10:34 (PluginManager OSGi > > > Framework) we could start to work towards getting Felix running inside > > > another OSGi framework. I can see no technical reason why an OSGi > > > BundleContext cannot be loaded as a child of another BundleContext, > > > i.e. Felix embedde4d inside Equinox or Spring dm or whatever. Do you > > > have a stack trace or some more logs that you could attach to a new > > > JIRA? > > > > > > Cheers, > > > Andrew. > > > > > > > -- > > 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/ > > technical blog : > > http://danushkastechythoughts.blogspot.com/ > > twitter : > > http://twitter.com/danushkamenik > > linkedin : > > http://lk.linkedin.com/in/danushka > > > --002215048e77ddbe3f048a67b144--