[prev in list] [next in list] [prev in thread] [next in thread] 

List:       ws-general
Subject:    Re: [Axis2] Add XmlSchema, Neethi, Axiom to TLP Proposal
From:       "Davanum Srinivas" <davanum () gmail ! com>
Date:       2008-11-10 0:23:38
Message-ID: 19e0530f0811091623m772d9466l17e4d52c7fdc2c09 () mail ! gmail ! com
[Download RAW message or body]

Eran,

You are falling behind :) Yes, please see latest TLP proposal on wiki.
Yes, Axiom is not moving.

-- dims

On Sun, Nov 9, 2008 at 6:39 PM, Eran Chinthaka <eran.chinthaka@gmail.com> wrote:
>
>
> On Mon, Nov 3, 2008 at 12:11 PM, Glen Daniels <glen@thoughtcraft.com> wrote:
>>
>> Daniel Kulp wrote:
>>>
>>> On Monday 03 November 2008 10:14:30 am Davanum Srinivas wrote:
>>>>
>>>> Glen,
>>>>
>>>> Was looking at
>>>> http://wiki.apache.org/ws/FrontPage/Proposals/Axis2TLPProposal
>>>>
>>>> Any thoughts on why leave behind XmlSchema, Neethi, Axiom?
>>>
>>> Because they are used by several other projects that have nothing to do
>>> with Axis 2?
>
> This is not a good argument, at least for me. We are using lots of
> components, like mail implementation from Geronimo project. But are they on
> Geronimo commons? Aren't we accessing them, even when they are within
> Geronimo? Is it a must to have them separate?
>
> So whats the problem of moving Axiom, Neethi also in to Axis2 project. As
> one said, a change in Axiom might most probably affect Axis2 as well.
>
> There are two more reasons I have *for* moving Axiom also in to Axis2
> project *if* Axis2 becomes a TLP.
>
> 1. Axiom has a SOAP implementation which was done because of Axis2. If one
> needs to leave Axiom inside WS, during this movement, then some one please
> move the SOAP part out of Axiom. If the argument is Axiom is a pure XML
> object model so that others can use it, then please move out the SOAP part
> from Axiom.
> Please note that I'm not saying anything bad about Axiom having a SOAP
> implementation. We did it because we targeted Axiom for Axis2.
>
> 2.  In another thread, it was suggested to make POLOKA a sub-project of
> Axis2, because
>  i) it *will* have Axis2 compatible eventing implementation
> ii) and (may be) it is Web service based implementation. (please correct me
> if I'm wrong)
>
> If the argument for leaving some projects within WS project, and taking with
> Axis2 is about Axis2 dependencies, then why should we move Poloka (when it
> is graduated) in to Axis2. Its just another project, which has a *plugin*
> (as I think) to work with Axis2.
> if this is the case, then I will argue that Synapse also should come under
> Axis2. Abdera should come in to Axiom.
>
> I am seriously missing something somewhere.
>
> Thanks,
> Chinthaka
>
>



-- 
Davanum Srinivas :: http://davanum.wordpress.com

---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@ws.apache.org
For additional commands, e-mail: general-help@ws.apache.org

[prev in list] [next in list] [prev in thread] [next in thread]