Return-Path: Delivered-To: apmail-felix-users-archive@minotaur.apache.org Received: (qmail 82205 invoked from network); 10 Sep 2010 13:20:58 -0000 Received: from unknown (HELO mail.apache.org) (140.211.11.3) by 140.211.11.9 with SMTP; 10 Sep 2010 13:20:58 -0000 Received: (qmail 62463 invoked by uid 500); 10 Sep 2010 13:20:57 -0000 Delivered-To: apmail-felix-users-archive@felix.apache.org Received: (qmail 62234 invoked by uid 500); 10 Sep 2010 13:20:55 -0000 Mailing-List: contact users-help@felix.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@felix.apache.org Delivered-To: mailing list users@felix.apache.org Received: (qmail 62216 invoked by uid 99); 10 Sep 2010 13:20:54 -0000 Received: from Unknown (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 10 Sep 2010 13:20:54 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of heavy@ungoverned.org designates 67.222.54.6 as permitted sender) Received: from [67.222.54.6] (HELO cpoproxy3-pub.bluehost.com) (67.222.54.6) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 10 Sep 2010 13:20:30 +0000 Received: (qmail 11770 invoked by uid 0); 10 Sep 2010 13:20:09 -0000 Received: from unknown (HELO host118.hostmonster.com) (74.220.207.118) by cpoproxy3.bluehost.com with SMTP; 10 Sep 2010 13:20:09 -0000 DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=default; d=ungoverned.org; h=Received:Message-ID:Date:From:User-Agent:MIME-Version:To:Subject:References:In-Reply-To:Content-Type:Content-Transfer-Encoding:X-Identified-User; b=d59yvdanyZNRj6KUmq3uikYe1mI/pUSLftKoSY0F0YiKII03IHJ8pVU5x4f5uEHQ+KwFUgSkYukiwpScAwgQhcrOGHNqyvh+5liOsQ9ow8H/x/1Pc8bOddr0ldeOo4s/; Received: from [99.62.222.230] (helo=heavyweight.glastender.com) by host118.hostmonster.com with esmtpsa (TLSv1:AES256-SHA:256) (Exim 4.69) (envelope-from ) id 1Ou3WS-00050x-Lc for users@felix.apache.org; Fri, 10 Sep 2010 07:20:08 -0600 Message-ID: <4C8A3086.60104@ungoverned.org> Date: Fri, 10 Sep 2010 09:20:06 -0400 From: "Richard S. Hall" User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.9) Gecko/20100825 Lightning/1.0b2 Thunderbird/3.1.3 MIME-Version: 1.0 To: users@felix.apache.org Subject: Re: Running felix on Gentoo References: <4C88E66E.9040800@ungoverned.org> <4F4C5FEE-A90B-4AB2-B212-E3AE548FD794@id.ethz.ch> <4C8977A6.2060603@ungoverned.org> <33BD867D-DE56-4D03-A4EF-E6DCC1B3DD87@id.ethz.ch> In-Reply-To: <33BD867D-DE56-4D03-A4EF-E6DCC1B3DD87@id.ethz.ch> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Identified-User: {1027:host118.hostmonster.com:ungovern:ungoverned.org} {sentby:smtp auth 99.62.222.230 authed with heavy@ungoverned.org} X-Virus-Checked: Checked by ClamAV on apache.org On 9/10/10 5:15, Wunden Tobias wrote: > The only thing that I don't understand is that if Felix really is only loading bundles, then why should a bundle make assumptions about it's runtime environment (daemon vs. interactive) and shut down the whole framework if these assumptions don't hold. t just seems strange to me, which is likely to mean that I don't understand the design rather than the design being wrong :-) The Felix framework is only loading bundles. Actually, the launcher is creating a framework instance and installing/starting any bundles contained in the bundle/ directory. The framework by itself won't load any bundles at all. In this particular case, I don't believe that Gogo is shutting down the entire framework, it is just grabbing stdin. In general, you are correct, bundles shouldn't make assumptions about what they are allowed to do; for example, you can't stop bundles from calling System.exit() unless you plan to enable security. But the shell bundle is somewhat special in this case. The distribution we provide of the Felix framework is intended to be a developer distribution, which will typically be used in an interactive way by a developer. If you don't want Gogo grabbing stdin, then you should either a) not deploy it or b) configure it not to do so. But from a development perspective, it is doing exactly what we want, since we don't want a headless developer distribution. Keep in mind, the situation would be no different for a bundle wanting to display a GUI. In your case, you also wouldn't want this. The OSGi framework is a generic module layer, you can build any type of application with it (interactive or not, server or client, etc.), so everything a bundle does is based on some assumption about how it is going to be used. -> richard > Again, thanks for your quick (and patient) help! > > Tobias > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscribe@felix.apache.org > For additional commands, e-mail: users-help@felix.apache.org > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@felix.apache.org For additional commands, e-mail: users-help@felix.apache.org