Return-Path: 
 <axis-dev-return-72984-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 32269 invoked from network); 7 Oct 2008 01:19:55 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 7 Oct 2008 01:19:55 -0000
Received: (qmail 46286 invoked by uid 500); 7 Oct 2008 01:19:44 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 46201 invoked by uid 500); 7 Oct 2008 01:19:44 -0000
Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
list-help: <mailto:axis-dev-help@ws.apache.org>
list-unsubscribe: <mailto:axis-dev-unsubscribe@ws.apache.org>
List-Post: <mailto:axis-dev@ws.apache.org>
List-Id: <axis-dev.ws.apache.org>
Delivered-To: mailing list axis-dev@ws.apache.org
Received: (qmail 46174 invoked by uid 99); 7 Oct 2008 01:19:44 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 06 Oct 2008 18:19:44 -0700
X-ASF-Spam-Status: No, hits=2.1 required=10.0
	tests=DNS_FROM_SECURITYSAGE,HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of ruwan.linton@gmail.com
 designates 209.85.142.184 as permitted sender)
Received: from [209.85.142.184] (HELO ti-out-0910.google.com) (209.85.142.184)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 07 Oct 2008 01:18:39 +0000
Received: by ti-out-0910.google.com with SMTP id y6so2300830tia.18
        for <axis-dev@ws.apache.org>; Mon, 06 Oct 2008 18:18:57 -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:to
         :subject:mime-version:content-type;
        bh=2k5nULDiUlNeVbOVkU/2SMbZQtyL96bABLhfaPis664=;
        b=j4LwE0ZudphOGEEcOHUVasd04bs/rmaseoBkr4JzHjkBr8gnYRs8d49iWaIf8ad+V+
         gJ9wQ+4NzroeH15YjezbVVC9rpJY8ikemqm80r2wqY8WlkTvYq7joZ8N7yqg6xkrvJji
         Jcx87ejO8bVO51JBJLzDvfpgtuUo2laM2fTdE=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:mime-version:content-type;
        b=NYuieAUHibazTj7dXzAmzdf50/rlu1yjPZyR/MnBA+yUYzyuVJeWFWqVqx46X/5VTS
         ZKozDnYa0/14aeW3c0yzMKpm9Hu3gYowlVf+3dfwyaWQsz/OBeL1gbSFUa7sWjLUNGkR
         wO2E/sdzJNlFhy1hf30rNXrmiAOdJaYW3Xhm0=
Received: by 10.110.105.10 with SMTP id d10mr7370603tic.57.1223342337218;
        Mon, 06 Oct 2008 18:18:57 -0700 (PDT)
Received: by 10.110.10.13 with HTTP; Mon, 6 Oct 2008 18:18:57 -0700 (PDT)
Message-ID: <672a01200810061818v4df0f9cdgfc9d563ae90b4811@mail.gmail.com>
Date: Tue, 7 Oct 2008 06:48:57 +0530
From: "Ruwan Linton" <ruwan.linton@gmail.com>
To: commons-dev@ws.apache.org, dev@synapse.apache.org,
	"axis-dev@ws.apache.org" <axis-dev@ws.apache.org>
Subject: Transport jars as OSGi bundles
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_70595_14499635.1223342337203"
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_70595_14499635.1223342337203
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi devs,

I would like to propose the transport jar artifacts to be OSGi bundles,
because synapse artifacts are OSGi bundles so that in an OSGi container we
should be able to use these transport jar artifacts as OSGi bundles
effectively.

I would like to do this... since I did the same for synapse artifacts.
Making these artifacts OSGi bundles doesn't affect the normal existing non
OSGi operation of the jar artifacts. Basically we will be having a jar
artifact with some more information on the MANIFEST ...

Thanks,
Ruwan

-- 
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/

------=_Part_70595_14499635.1223342337203
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

<div dir="ltr">Hi devs,<br><br>I would like to propose the transport jar artifacts to be OSGi bundles, because synapse artifacts are OSGi bundles so that in an OSGi container we should be able to use these transport jar artifacts as OSGi bundles effectively.<br>
<br>I would like to do this... since I did the same for synapse artifacts. Making these artifacts OSGi bundles doesn&#39;t affect the normal existing non OSGi operation of the jar artifacts. Basically we will be having a jar artifact with some more information on the MANIFEST ...<br>
<br>Thanks,<br>Ruwan <br clear="all"><br>-- <br>Ruwan Linton<br><a href="http://wso2.org">http://wso2.org</a> - &quot;Oxygenating the Web Services Platform&quot;<br><a href="http://ruwansblog.blogspot.com/">http://ruwansblog.blogspot.com/</a><br>

</div>

------=_Part_70595_14499635.1223342337203--