Return-Path: Delivered-To: apmail-tomcat-dev-archive@www.apache.org Received: (qmail 65099 invoked from network); 23 Apr 2008 17:03:05 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 23 Apr 2008 17:03:05 -0000 Received: (qmail 4665 invoked by uid 500); 23 Apr 2008 17:03:02 -0000 Delivered-To: apmail-tomcat-dev-archive@tomcat.apache.org Received: (qmail 4605 invoked by uid 500); 23 Apr 2008 17:03:02 -0000 Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Tomcat Developers List" Delivered-To: mailing list dev@tomcat.apache.org Received: (qmail 4594 invoked by uid 99); 23 Apr 2008 17:03:02 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2008 10:03:02 -0700 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of costin@gmail.com designates 216.239.58.187 as permitted sender) Received: from [216.239.58.187] (HELO gv-out-0910.google.com) (216.239.58.187) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Apr 2008 17:02:18 +0000 Received: by gv-out-0910.google.com with SMTP id n40so404421gve.39 for ; Wed, 23 Apr 2008 10:01:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; bh=aK/sO2GywHaagVSxxSrn4CBF7XDvXApXt2tbV6BhYdM=; b=IcrtmvxmPGgOR+X3UQfyzG1ETD8WKF4u8GSz9nGdOh7kIJycJ17OPIv8tGY+wjAKwY9RlXpqLlxUmUWZuGTlZS2DzyZBFkQwSasYsWpnJHo5fbBnZrigmnJBx/6elhA5Kf3ckn13isaUw4l4AW33AzNCvWV6JgBR8TZRqkyypYA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=message-id:date:from:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth; b=cZFuy7rjt/ao2c1kCRFOIwYErp4Gqg9pN5vWf5fWSb8wb01cwI1anJirBq9mxBXJ9sbKfqZKK0x3+8lSB9iSZDUet2kSXAMKU2emgXIVzqTs+MpciWhSQO24fsfMnMKfUCxxGC7i0ca9Mb3/RryRb9ERT1uf9OaPzJoue4dHGpY= Received: by 10.82.118.2 with SMTP id q2mr1333803buc.85.1208970097373; Wed, 23 Apr 2008 10:01:37 -0700 (PDT) Received: by 10.82.100.3 with HTTP; Wed, 23 Apr 2008 10:01:37 -0700 (PDT) Message-ID: <96e4b5230804231001he40cd16q67e7fb21a2b95393@mail.gmail.com> Date: Wed, 23 Apr 2008 10:01:37 -0700 From: "Costin Manolache" Sender: costin@gmail.com To: "Tomcat Developers List" Subject: Re: Osgifing Tomcat In-Reply-To: <6291fc850804230836l35a7fd44yfae52464ab282dc7@mail.gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <6291fc850804220345w746f8b5cwc98eba9fbc5bcb14@mail.gmail.com> <480EE810.9040005@objectweb.org> <6291fc850804230056x7c43ba61rd9258879066f5887@mail.gmail.com> <480EFCE6.6040304@hanik.com> <480EFF7E.5010905@objectweb.org> <6291fc850804230524o61b48de3x65c9b6da8f8e47ce@mail.gmail.com> <480F4111.9080703@objectweb.org> <1208962152.3303.99.camel@localhost.localdomain> <96e4b5230804230830r67ae11c1x295ac2037e657c11@mail.gmail.com> <6291fc850804230836l35a7fd44yfae52464ab282dc7@mail.gmail.com> X-Google-Sender-Auth: aedcb65193cc8f52 X-Virus-Checked: Checked by ClamAV on apache.org On Wed, Apr 23, 2008 at 8:36 AM, Henri Gomez wrote: > > Silly question, but did experiments with OSGI could be done, first, in > tomcatlight ? > I'm not sure it's the best idea, my goal is to move it out of sandbox, it already has enough experiments that need completion. and the main goal is to be 'lite' :-). It has a simple Addon mechanism, and I don't mind having an optional addon manager impl using OSGI - but I don't want to get distracted, I started tomcat-lite experiment >2 years ago. The first part ( adding manifests to existing tomcat ) seems to have support so could be done in the trunk. I don't see any reason for having non-intrusive OSGI support developed in sandbox - as long as the code is in a package that is excluded from the official distro, and is released as a separate unit it could live in trunk. It'll need the 3 +1 to be released, of course - but the whole point of modularity is to be able to develop modules independent of the container. IMO sandbox is for experiments that would replace existing tomcat components or core stuff. If you do it in trunk - it's easier to get it released eventually, and you may get better reviews and attention. Costin --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org For additional commands, e-mail: dev-help@tomcat.apache.org