Return-Path: 
 <axis-dev-return-75827-apmail-ws-axis-dev-archive=ws.apache.org@ws.apache.org>
Delivered-To: apmail-ws-axis-dev-archive@www.apache.org
Received: (qmail 4008 invoked from network); 20 Jun 2009 09:17:32 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 20 Jun 2009 09:17:32 -0000
Received: (qmail 79875 invoked by uid 500); 20 Jun 2009 09:17:42 -0000
Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org
Received: (qmail 79712 invoked by uid 500); 20 Jun 2009 09:17:42 -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 79579 invoked by uid 99); 20 Jun 2009 09:17:41 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Jun 2009 09:17:41 +0000
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 andreas.veithen@gmail.com
 designates 209.85.218.214 as permitted sender)
Received: from [209.85.218.214] (HELO mail-bw0-f214.google.com)
 (209.85.218.214)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 20 Jun 2009 09:17:31 +0000
Received: by bwz10 with SMTP id 10so2419240bwz.16
        for <multiple recipients>; Sat, 20 Jun 2009 02:17:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:in-reply-to:references
         :date:message-id:subject:from:to:cc:content-type
         :content-transfer-encoding;
        bh=g/J5nfUuqEeid174QRNYM6Q4VQ99RF+BxsyhK/iIFCU=;
        b=TQFn/5YBMsJkZ4DNI/YrVxCHYqgdhukrHhPhaqP9l/cUoRo2ZNWgCRhmd19mWm95U/
         SXGX5VT4U99v72MMuXfm6JeTtKdVP8yD/qgYKLdjcSsv0HmFRc6iqegrnXX/xYHe2m0p
         UQV1fg4ujbm4UUmKOubLchNz9b5rcTh9raTfk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type:content-transfer-encoding;
        b=w7Yd2xzagnny1DIbEt82dU8I1Wkr1tE44uvzqtRzNlo3glb0vrIqBGirv4URmeON/K
         OtGt93afWGAI57ymvSKJuswCbIOFTLSvA1cFGTgUADf1wjJcAIsIhij3bg1+7RPMyXiQ
         2Ymh4RjyPgYYOhV7gIMi+8zSgec6W6zeGDMAM=
MIME-Version: 1.0
Received: by 10.239.163.69 with SMTP id o5mr290897hbd.40.1245489429276; Sat,
	20 Jun 2009 02:17:09 -0700 (PDT)
In-Reply-To: <4A900FD01198475F8003D707DEF5C69A@rfengt61p>
References: <7E59C1B6D01C4723B5F67C920BFBA375@rfengt61p>
	 <71e1b5740906190148t35fd759dg28b45e9bcc9e5c83@mail.gmail.com>
	 <4A3B6934.4060300@gmail.com>
	 <4A900FD01198475F8003D707DEF5C69A@rfengt61p>
Date: Sat, 20 Jun 2009 11:17:09 +0200
Message-ID: <b67458760906200217h1658b5c7ja35c6efec4babfff@mail.gmail.com>
Subject: Re: Axis2/Axiom/Woden OSGi bundle issues, was: Re: Treat axis2
	bundles as plain jars
From: Andreas Veithen <andreas.veithen@gmail.com>
To: axis-dev@ws.apache.org
Cc: dev@tuscany.apache.org, commons-dev@ws.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
X-Virus-Checked: Checked by ClamAV on apache.org

Raymond,

Can you please open JIRA reports for the remaining issues you see in
Axiom? I will be happy to work with you to fix them.

Andreas

On Fri, Jun 19, 2009 at 19:04, Raymond Feng<enjoyjava@gmail.com> wrote:
> Hi,
>
> The following is a list of issues we ran into. Some of the issues might h=
ave
> been resolved by Axis2 1.5. I have tried to bring some of them to the
> attentions of Axis2 community but it doesn't seem to be very responsive i=
n
> the OSGi area :-(.
>
> With Axis2 1.4.1, we have experienced quite a few issues related to OSGi,
> especially in the following areas:
>
> 1) Some of the axis2 jars (such as axis2-kernel) are OSGi bundles while
> others (such as axis2-mtompolicy) are not.
>
> Axis2 1.5 now has a bundle org.apache.axis2.osgi. I posted a question to =
the
> Axis2 dev ML to understand if we should use that one instead of individua=
l
> jars but no responses. See:
> http://www.mail-archive.com/axis-dev@ws.apache.org/msg46269.html.
>
> 2) Axis2 jars have split packages, for example, axis2-kernel and axis2-ad=
b
> both have the org.apache.axis2.util package.
>
> 3) Some of the Axis2/AXIOM code uses the JAR service provider pattern to
> instantiate factories such as XMLInputFactory.newInstance(),
> DocumentBuilderFactory.newInstance(). These methods depends on the TCCL
> which is not OSGi friendly at all.
>
> 4) Some of the Axis2 bundles imports "private" packages from xercesImpl,
> xalan or woden (Seems to be cleaner in 1.5)
> woden-impl-dom still has the issues.
>
> 5) We plugin message receivers in axis2.xml. But Axis2 doesn't have a goo=
d
> way to load the classes outside of Axis2 bundles.
>
> 6) Axiom bundle is missing Import-Package to soap11 and soap12 factories.
> (Fixed in 1.2.8)
>
> 7) Axiom-api 1.2.8 is missing OSGi Import-Package to javax.xml.stream.uti=
l
> under JDK 1.5:
> https://issues.apache.org/jira/browse/WSCOMMONS-462 (fixed)
>
> Unresolved issues:
> https://issues.apache.org/jira/browse/AXIS2-4311
> https://issues.apache.org/jira/browse/AXIS2-4310
>
> Thanks,
> Raymond
> --------------------------------------------------
> From: "Davanum Srinivas" <davanum@gmail.com>
> Sent: Friday, June 19, 2009 3:32 AM
> To: <dev@tuscany.apache.org>
> Subject: Re: Treat axis2 bundles as plain jars
>
>> +1 :)
>>
>> -- dims
>>
>> On 06/19/2009 04:48 AM, ant elder wrote:
>>>
>>> How about giving axis2/axiom/woden patches to fix the manifests for
>>> what we need?
>>>
>>> =A0 ...ant
>>>
>>> On Thu, Jun 18, 2009 at 10:15 PM, Raymond Feng<enjoyjava@gmail.com>
>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> The axis2/axiom/woden OSGi bundles are half-baked. We have run into ma=
ny
>>>> issues for the OSGi dependencies. Since then some workarounds are
>>>> introduced
>>>> to make them working with Tuscany in the OSGi environment, such as
>>>> declaring
>>>> some of the Tuscany bundles are fragments to axis2/axiom bundles to fi=
x
>>>> import/export packages. That causes new problems such as PDE fragment
>>>> package visibility and circular dependencies.
>>>>
>>>> I'm really tired of the bogus MFs. Then it came into my mind that we c=
an
>>>> just treat them as plain jars and generate the MF for them. I got the
>>>> whole
>>>> thing working on this path with the following changes. Both maven,
>>>> Eclipse
>>>> PDE and Tuscany runtime are happy now.
>>>>
>>>> * The support for our maven-bundle-plugin to override the 3rd party
>>>> bundles:
>>>> http://svn.apache.org/viewvc?rev=3D786257&view=3Drev
>>>> * Customize the MF for axiom-api:
>>>> http://svn.apache.org/viewvc?rev=3D786263&view=3Drev
>>>> * Fix the MFs to bring up axis2 binding.ws:
>>>> http://svn.apache.org/viewvc?rev=3D786265&view=3Drev
>>>>
>>>> OSGi is fun :-(
>>>>
>>>> Thanks,
>>>> Raymond
>>>>
>