You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ws.apache.org by Sagara Gunathunga <sa...@gmail.com> on 2012/06/23 17:55:15 UTC
[WODEN] Future of Woden Axiom implementation ?
Hi Devs,
I'm thinking about future of Axiom (OM) based implementation of Woden
API for sometime, whether we should continue or drop support from next
release ?
AFAIK original objective of OM implementation is to support Axis2 but
in fact Axis2 never used OM implementation instead Axis2 still use DOM
based implementation. Also in my POV there is no such drawbacks with
DOM implementation to move Axis2 to use OM implementation. At the
moment there is no clear indication about users of OM implementation
too. In this situation it is kind of a overhead to maintain OM
implementation further specially with small number of developers. At
the beginning Woden had plans for number of cool features such as
supporting to both WSDL versions etc, but all original developers have
been disappeared from the community few years ago hence it's seem OK
to re-prioritize objectives based on current requirements and
resources.
This also important decision to reduce complexities among Woden
artifacts, at the moment it's required to have at least 3 JAR files
to use Woden framework as woden-api, woden-impl-common and
woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
merge these artifacts and deliver above 3 module as a single JAR file
called woden.jar. IMO this kind of single artifact deliverables are
more natural for utility projects and easy to deploy on OGSI
containers too.
Personally I don't have energy to maintain both implementations, also
without actual users no point to maintain OM implementation further.
Based on above facts I would like to suggest terminate OM support from
next release and move forward the project with what ever the useful
features.
Any thoughts ?
Thanks !
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
LinkedIn - http://www.linkedin.com/in/ssagara
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
Re: [WODEN] Future of Woden Axiom implementation ?
Posted by Sagara Gunathunga <sa...@gmail.com>.
Sound good, I will proceed with required changes.
Thanks !
On Tue, Jun 26, 2012 at 3:06 AM, Andreas Veithen
<an...@gmail.com> wrote:
> I think it makes sense to remove the Axiom support. There are two
> reasons for that:
>
> 1. Axiom enables a couple of optimizations (deferred parsing,
> pull-through and sourced elements) that don't exist in DOM. However, I
> don't see how Woden (or code that uses Woden) would benefit from these
> optimizations.
>
> 2. We have a DOM compatible Axiom implementation (although the level
> of DOM compliance is currently not very high). Also, I think that at
> some point in the future, the default Axiom implementation will
> support DOM (with a decent level of compliance).
>
> Andreas
>
> On Sat, Jun 23, 2012 at 5:55 PM, Sagara Gunathunga
> <sa...@gmail.com> wrote:
>> Hi Devs,
>>
>> I'm thinking about future of Axiom (OM) based implementation of Woden
>> API for sometime, whether we should continue or drop support from next
>> release ?
>>
>> AFAIK original objective of OM implementation is to support Axis2 but
>> in fact Axis2 never used OM implementation instead Axis2 still use DOM
>> based implementation. Also in my POV there is no such drawbacks with
>> DOM implementation to move Axis2 to use OM implementation. At the
>> moment there is no clear indication about users of OM implementation
>> too. In this situation it is kind of a overhead to maintain OM
>> implementation further specially with small number of developers. At
>> the beginning Woden had plans for number of cool features such as
>> supporting to both WSDL versions etc, but all original developers have
>> been disappeared from the community few years ago hence it's seem OK
>> to re-prioritize objectives based on current requirements and
>> resources.
>>
>> This also important decision to reduce complexities among Woden
>> artifacts, at the moment it's required to have at least 3 JAR files
>> to use Woden framework as woden-api, woden-impl-common and
>> woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
>> merge these artifacts and deliver above 3 module as a single JAR file
>> called woden.jar. IMO this kind of single artifact deliverables are
>> more natural for utility projects and easy to deploy on OGSI
>> containers too.
>>
>> Personally I don't have energy to maintain both implementations, also
>> without actual users no point to maintain OM implementation further.
>> Based on above facts I would like to suggest terminate OM support from
>> next release and move forward the project with what ever the useful
>> features.
>>
>> Any thoughts ?
>>
>>
>> Thanks !
>> --
>> Sagara Gunathunga
>>
>> Blog - http://ssagara.blogspot.com
>> Web - http://people.apache.org/~sagara/
>> LinkedIn - http://www.linkedin.com/in/ssagara
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: dev-help@ws.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: dev-help@ws.apache.org
>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
LinkedIn - http://www.linkedin.com/in/ssagara
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
Fwd: [WODEN] Future of Woden Axiom implementation ?
Posted by Sagara Gunathunga <sa...@gmail.com>.
Woden and WS developers discussing about to drop Axiom based Woden
implementation from next release. This is basically due to no
indication from users about use of this implementation and maintenance
overhead. We believe drop unused components and maintain/develop
what ever the useful components is a important step to keep Woden
project healthy.
We will continue to support Woden DOM based implantation and we would
like to know your thoughts on this ?
Thanks !
---------- Forwarded message ----------
From: Andreas Veithen <an...@gmail.com>
Date: Tue, Jun 26, 2012 at 3:06 AM
Subject: Re: [WODEN] Future of Woden Axiom implementation ?
To: dev@ws.apache.org
I think it makes sense to remove the Axiom support. There are two
reasons for that:
1. Axiom enables a couple of optimizations (deferred parsing,
pull-through and sourced elements) that don't exist in DOM. However, I
don't see how Woden (or code that uses Woden) would benefit from these
optimizations.
2. We have a DOM compatible Axiom implementation (although the level
of DOM compliance is currently not very high). Also, I think that at
some point in the future, the default Axiom implementation will
support DOM (with a decent level of compliance).
Andreas
On Sat, Jun 23, 2012 at 5:55 PM, Sagara Gunathunga
<sa...@gmail.com> wrote:
> Hi Devs,
>
> I'm thinking about future of Axiom (OM) based implementation of Woden
> API for sometime, whether we should continue or drop support from next
> release ?
>
> AFAIK original objective of OM implementation is to support Axis2 but
> in fact Axis2 never used OM implementation instead Axis2 still use DOM
> based implementation. Also in my POV there is no such drawbacks with
> DOM implementation to move Axis2 to use OM implementation. At the
> moment there is no clear indication about users of OM implementation
> too. In this situation it is kind of a overhead to maintain OM
> implementation further specially with small number of developers. At
> the beginning Woden had plans for number of cool features such as
> supporting to both WSDL versions etc, but all original developers have
> been disappeared from the community few years ago hence it's seem OK
> to re-prioritize objectives based on current requirements and
> resources.
>
> This also important decision to reduce complexities among Woden
> artifacts, at the moment it's required to have at least 3 JAR files
> to use Woden framework as woden-api, woden-impl-common and
> woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
> merge these artifacts and deliver above 3 module as a single JAR file
> called woden.jar. IMO this kind of single artifact deliverables are
> more natural for utility projects and easy to deploy on OGSI
> containers too.
>
> Personally I don't have energy to maintain both implementations, also
> without actual users no point to maintain OM implementation further.
> Based on above facts I would like to suggest terminate OM support from
> next release and move forward the project with what ever the useful
> features.
>
> Any thoughts ?
>
>
> Thanks !
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> LinkedIn - http://www.linkedin.com/in/ssagara
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
LinkedIn - http://www.linkedin.com/in/ssagara
Re: [WODEN] Future of Woden Axiom implementation ?
Posted by Andreas Veithen <an...@gmail.com>.
I think it makes sense to remove the Axiom support. There are two
reasons for that:
1. Axiom enables a couple of optimizations (deferred parsing,
pull-through and sourced elements) that don't exist in DOM. However, I
don't see how Woden (or code that uses Woden) would benefit from these
optimizations.
2. We have a DOM compatible Axiom implementation (although the level
of DOM compliance is currently not very high). Also, I think that at
some point in the future, the default Axiom implementation will
support DOM (with a decent level of compliance).
Andreas
On Sat, Jun 23, 2012 at 5:55 PM, Sagara Gunathunga
<sa...@gmail.com> wrote:
> Hi Devs,
>
> I'm thinking about future of Axiom (OM) based implementation of Woden
> API for sometime, whether we should continue or drop support from next
> release ?
>
> AFAIK original objective of OM implementation is to support Axis2 but
> in fact Axis2 never used OM implementation instead Axis2 still use DOM
> based implementation. Also in my POV there is no such drawbacks with
> DOM implementation to move Axis2 to use OM implementation. At the
> moment there is no clear indication about users of OM implementation
> too. In this situation it is kind of a overhead to maintain OM
> implementation further specially with small number of developers. At
> the beginning Woden had plans for number of cool features such as
> supporting to both WSDL versions etc, but all original developers have
> been disappeared from the community few years ago hence it's seem OK
> to re-prioritize objectives based on current requirements and
> resources.
>
> This also important decision to reduce complexities among Woden
> artifacts, at the moment it's required to have at least 3 JAR files
> to use Woden framework as woden-api, woden-impl-common and
> woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
> merge these artifacts and deliver above 3 module as a single JAR file
> called woden.jar. IMO this kind of single artifact deliverables are
> more natural for utility projects and easy to deploy on OGSI
> containers too.
>
> Personally I don't have energy to maintain both implementations, also
> without actual users no point to maintain OM implementation further.
> Based on above facts I would like to suggest terminate OM support from
> next release and move forward the project with what ever the useful
> features.
>
> Any thoughts ?
>
>
> Thanks !
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> LinkedIn - http://www.linkedin.com/in/ssagara
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
Re: [WODEN] Future of Woden Axiom implementation ?
Posted by Lawrence Mandel <lm...@gmail.com>.
Hi Sagara,
If you're correct that there are no current consumers of the Axiom impl of
Woden I think your proposal makes good sense. Best to focus the efforts of
the small number of active contributors on a code base that sees usage.
Lawrence
On Sat, Jun 23, 2012 at 11:55 AM, Sagara Gunathunga <
sagara.gunathunga@gmail.com> wrote:
> Hi Devs,
>
> I'm thinking about future of Axiom (OM) based implementation of Woden
> API for sometime, whether we should continue or drop support from next
> release ?
>
> AFAIK original objective of OM implementation is to support Axis2 but
> in fact Axis2 never used OM implementation instead Axis2 still use DOM
> based implementation. Also in my POV there is no such drawbacks with
> DOM implementation to move Axis2 to use OM implementation. At the
> moment there is no clear indication about users of OM implementation
> too. In this situation it is kind of a overhead to maintain OM
> implementation further specially with small number of developers. At
> the beginning Woden had plans for number of cool features such as
> supporting to both WSDL versions etc, but all original developers have
> been disappeared from the community few years ago hence it's seem OK
> to re-prioritize objectives based on current requirements and
> resources.
>
> This also important decision to reduce complexities among Woden
> artifacts, at the moment it's required to have at least 3 JAR files
> to use Woden framework as woden-api, woden-impl-common and
> woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
> merge these artifacts and deliver above 3 module as a single JAR file
> called woden.jar. IMO this kind of single artifact deliverables are
> more natural for utility projects and easy to deploy on OGSI
> containers too.
>
> Personally I don't have energy to maintain both implementations, also
> without actual users no point to maintain OM implementation further.
> Based on above facts I would like to suggest terminate OM support from
> next release and move forward the project with what ever the useful
> features.
>
> Any thoughts ?
>
>
> Thanks !
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> LinkedIn - http://www.linkedin.com/in/ssagara
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: dev-help@ws.apache.org
>
>
RE: [WODEN] Future of Woden Axiom implementation ?
Posted by Martin Gainty <mg...@hotmail.com>.
Hello Jochen
apparently I am the only person that has implemented axiom in a live commercial implementation so clearly i hold a minority opinion
I agree there are alot more constructive use of devs time and effort than say pulling an dependent subsystem but
if every enhancement forces you to duplicate every dom integration effort with woden integration
then a strong case can be made to the panelists to support the stronger more stable subsystem and drop support for the dupe subsystem
(best if we could see see a matrix to verify woden and dom featuresets are indeed identical)
On a side note here is what I see are Axis 3 main drawbacks in order of priority
1)antiquated use of build.xml in build scripts instead of refactoring all builds to version aware SCM e.g. maven (3)..server and client scripts are all ant based..
2)lack of esb
3)process lacks adherence to apache vote by democracy rules..one person says 'do it' and then another makes vast sweeping changes to working code
without bothering to put the effort to a vote (majority wins) for a fixed period of time (usually 72 hours)..sagara has graciously revived the apache process
with his request for comment on deprecating woden
Granted alot of people are going on vaca now (including myself) so resources (peoples time to research,design and code, test and integrate) are limited
but we need to address the axis2 community collectively to gain consensus for each effort before committing sweeping changes
The end result *should be* increased adoption of Axis2 in the SAAS community
WDYT
Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
> Date: Wed, 27 Jun 2012 09:45:38 +0200
> Subject: Re: [WODEN] Future of Woden Axiom implementation ?
> From: jochen.wiedmann@gmail.com
> To: dev@ws.apache.org
>
> Question: Are there any ongoing developments: If not, I'd say we leave
> the code and avoid annoying potential users.
>
> Otherwise: If we might save work ourselves, drop it. (Don't forget to
> increment the major version number and possibly change Maven GID and
> package to indicate incompatible changes.)
>
>
> On Sat, Jun 23, 2012 at 5:55 PM, Sagara Gunathunga
> <sa...@gmail.com> wrote:
> > Hi Devs,
> >
> > I'm thinking about future of Axiom (OM) based implementation of Woden
> > API for sometime, whether we should continue or drop support from next
> > release ?
> >
> > AFAIK original objective of OM implementation is to support Axis2 but
> > in fact Axis2 never used OM implementation instead Axis2 still use DOM
> > based implementation. Also in my POV there is no such drawbacks with
> > DOM implementation to move Axis2 to use OM implementation. At the
> > moment there is no clear indication about users of OM implementation
> > too. In this situation it is kind of a overhead to maintain OM
> > implementation further specially with small number of developers. At
> > the beginning Woden had plans for number of cool features such as
> > supporting to both WSDL versions etc, but all original developers have
> > been disappeared from the community few years ago hence it's seem OK
> > to re-prioritize objectives based on current requirements and
> > resources.
> >
> > This also important decision to reduce complexities among Woden
> > artifacts, at the moment it's required to have at least 3 JAR files
> > to use Woden framework as woden-api, woden-impl-common and
> > woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
> > merge these artifacts and deliver above 3 module as a single JAR file
> > called woden.jar. IMO this kind of single artifact deliverables are
> > more natural for utility projects and easy to deploy on OGSI
> > containers too.
> >
> > Personally I don't have energy to maintain both implementations, also
> > without actual users no point to maintain OM implementation further.
> > Based on above facts I would like to suggest terminate OM support from
> > next release and move forward the project with what ever the useful
> > features.
> >
> > Any thoughts ?
> >
> >
> > Thanks !
> > --
> > Sagara Gunathunga
> >
> > Blog - http://ssagara.blogspot.com
> > Web - http://people.apache.org/~sagara/
> > LinkedIn - http://www.linkedin.com/in/ssagara
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: dev-help@ws.apache.org
> >
>
>
>
> --
> In other words: what could be seen as a socially debilitating failure
> of character can certainly work to your advantage too. (Linus
> Torvalds, but the use in the signature tells something about me as
> well.)
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: dev-help@ws.apache.org
>
Re: [WODEN] Future of Woden Axiom implementation ?
Posted by Jochen Wiedmann <jo...@gmail.com>.
Question: Are there any ongoing developments: If not, I'd say we leave
the code and avoid annoying potential users.
Otherwise: If we might save work ourselves, drop it. (Don't forget to
increment the major version number and possibly change Maven GID and
package to indicate incompatible changes.)
On Sat, Jun 23, 2012 at 5:55 PM, Sagara Gunathunga
<sa...@gmail.com> wrote:
> Hi Devs,
>
> I'm thinking about future of Axiom (OM) based implementation of Woden
> API for sometime, whether we should continue or drop support from next
> release ?
>
> AFAIK original objective of OM implementation is to support Axis2 but
> in fact Axis2 never used OM implementation instead Axis2 still use DOM
> based implementation. Also in my POV there is no such drawbacks with
> DOM implementation to move Axis2 to use OM implementation. At the
> moment there is no clear indication about users of OM implementation
> too. In this situation it is kind of a overhead to maintain OM
> implementation further specially with small number of developers. At
> the beginning Woden had plans for number of cool features such as
> supporting to both WSDL versions etc, but all original developers have
> been disappeared from the community few years ago hence it's seem OK
> to re-prioritize objectives based on current requirements and
> resources.
>
> This also important decision to reduce complexities among Woden
> artifacts, at the moment it's required to have at least 3 JAR files
> to use Woden framework as woden-api, woden-impl-common and
> woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
> merge these artifacts and deliver above 3 module as a single JAR file
> called woden.jar. IMO this kind of single artifact deliverables are
> more natural for utility projects and easy to deploy on OGSI
> containers too.
>
> Personally I don't have energy to maintain both implementations, also
> without actual users no point to maintain OM implementation further.
> Based on above facts I would like to suggest terminate OM support from
> next release and move forward the project with what ever the useful
> features.
>
> Any thoughts ?
>
>
> Thanks !
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> LinkedIn - http://www.linkedin.com/in/ssagara
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: dev-help@ws.apache.org
>
--
In other words: what could be seen as a socially debilitating failure
of character can certainly work to your advantage too. (Linus
Torvalds, but the use in the signature tells something about me as
well.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
Re: [WODEN] Future of Woden Axiom implementation ?
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Saturday, June 23, 2012, Deepal jayasinghe wrote:
> What is the status of WSDL 2.0 ? how many WS stacks use WSDL 2.0 ?.
WSDL 2.0 spec is kinda completed and became an official W3C recommendation
in 2007 but not widely adopted. AFAIK Axis2 is the only stack which support
for WSDL 2.0 fully.
Thanks !
>
> Deepal
> > Hi Devs,
> >
> > I'm thinking about future of Axiom (OM) based implementation of Woden
> > API for sometime, whether we should continue or drop support from next
> > release ?
> >
> > AFAIK original objective of OM implementation is to support Axis2 but
> > in fact Axis2 never used OM implementation instead Axis2 still use DOM
> > based implementation. Also in my POV there is no such drawbacks with
> > DOM implementation to move Axis2 to use OM implementation. At the
> > moment there is no clear indication about users of OM implementation
> > too. In this situation it is kind of a overhead to maintain OM
> > implementation further specially with small number of developers. At
> > the beginning Woden had plans for number of cool features such as
> > supporting to both WSDL versions etc, but all original developers have
> > been disappeared from the community few years ago hence it's seem OK
> > to re-prioritize objectives based on current requirements and
> > resources.
> >
> > This also important decision to reduce complexities among Woden
> > artifacts, at the moment it's required to have at least 3 JAR files
> > to use Woden framework as woden-api, woden-impl-common and
> > woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
> > merge these artifacts and deliver above 3 module as a single JAR file
> > called woden.jar. IMO this kind of single artifact deliverables are
> > more natural for utility projects and easy to deploy on OGSI
> > containers too.
> >
> > Personally I don't have energy to maintain both implementations, also
> > without actual users no point to maintain OM implementation further.
> > Based on above facts I would like to suggest terminate OM support from
> > next release and move forward the project with what ever the useful
> > features.
> >
> > Any thoughts ?
> >
> >
> > Thanks !
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org <javascript:;>
> For additional commands, e-mail: dev-help@ws.apache.org <javascript:;>
>
>
--
Sent from Gmail Mobile
RE: [WODEN] Future of Woden Axiom implementation ?
Posted by Martin Gainty <mg...@hotmail.com>.
if DOM version delivers the same functionality as WODEN then i agree with larry..further AXIOM development should implement DOM (and deprecate woden)
unless of course someone wants to fork the woden implementation!
Thanks,
Martin
______________________________________________
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni.
> From: sagara.gunathunga@gmail.com
> Date: Mon, 25 Jun 2012 10:56:32 +0530
> Subject: Re: [WODEN] Future of Woden Axiom implementation ?
> To: dev@ws.apache.org
>
> On Mon, Jun 25, 2012 at 5:10 AM, Martin Gainty <mg...@hotmail.com> wrote:
> > Ive have extensively implemented DOM4j based Axiom specifically:
> >
> > <groupId>org.apache.ws.commons.axiom</groupId>
> > <artifactId>axiom</artifactId>
> > <name>Axiom</name>
> > <version>1.2.9-SNAPSHOT</version>
> >
> >
> > I have'nt seen any matrix detailing the capabilities of axiom-woden vs
> > axiom-dom4j so I cannot say dropping woden would impact future Axiom
> > implementations
> > but it does seem like a duplication of effort to support both OM
> > implementations
> >
> > Is there a matrix available to illustrate features and
> > functions capabilities of axiom-woden vs axiom-dom4j?
>
> Please note that there is no DOM4J implementation available for
> Woden-API it's W3C DOM implementation for Woden-API. Functionality
> wise both implementations are more or less same but there is no matrix
> available.
>
> Thanks !
>
>
> > Martin
> > ------------------------------------
> > Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> > Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> > Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> > dient lediglich dem Austausch von Informationen und entfaltet keine
> > rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> > E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
> >
> >
> >
> >> Date: Sat, 23 Jun 2012 14:12:38 -0400
> >> From: deepalk@gmail.com
> >> To: dev@ws.apache.org
> >> Subject: Re: [WODEN] Future of Woden Axiom implementation ?
> >
> >>
> >> What is the status of WSDL 2.0 ? how many WS stacks use WSDL 2.0 ?.
> >>
> >> Deepal
> >> > Hi Devs,
> >> >
> >> > I'm thinking about future of Axiom (OM) based implementation of Woden
> >> > API for sometime, whether we should continue or drop support from next
> >> > release ?
> >> >
> >> > AFAIK original objective of OM implementation is to support Axis2 but
> >> > in fact Axis2 never used OM implementation instead Axis2 still use DOM
> >> > based implementation. Also in my POV there is no such drawbacks with
> >> > DOM implementation to move Axis2 to use OM implementation. At the
> >> > moment there is no clear indication about users of OM implementation
> >> > too. In this situation it is kind of a overhead to maintain OM
> >> > implementation further specially with small number of developers. At
> >> > the beginning Woden had plans for number of cool features such as
> >> > supporting to both WSDL versions etc, but all original developers have
> >> > been disappeared from the community few years ago hence it's seem OK
> >> > to re-prioritize objectives based on current requirements and
> >> > resources.
> >> >
> >> > This also important decision to reduce complexities among Woden
> >> > artifacts, at the moment it's required to have at least 3 JAR files
> >> > to use Woden framework as woden-api, woden-impl-common and
> >> > woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
> >> > merge these artifacts and deliver above 3 module as a single JAR file
> >> > called woden.jar. IMO this kind of single artifact deliverables are
> >> > more natural for utility projects and easy to deploy on OGSI
> >> > containers too.
> >> >
> >> > Personally I don't have energy to maintain both implementations, also
> >> > without actual users no point to maintain OM implementation further.
> >> > Based on above facts I would like to suggest terminate OM support from
> >> > next release and move forward the project with what ever the useful
> >> > features.
> >> >
> >> > Any thoughts ?
> >> >
> >> >
> >> > Thanks !
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: dev-help@ws.apache.org
> >>
>
>
>
> --
> Sagara Gunathunga
>
> Blog - http://ssagara.blogspot.com
> Web - http://people.apache.org/~sagara/
> LinkedIn - http://www.linkedin.com/in/ssagara
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: dev-help@ws.apache.org
>
Re: [WODEN] Future of Woden Axiom implementation ?
Posted by Sagara Gunathunga <sa...@gmail.com>.
On Mon, Jun 25, 2012 at 5:10 AM, Martin Gainty <mg...@hotmail.com> wrote:
> Ive have extensively implemented DOM4j based Axiom specifically:
>
> <groupId>org.apache.ws.commons.axiom</groupId>
> <artifactId>axiom</artifactId>
> <name>Axiom</name>
> <version>1.2.9-SNAPSHOT</version>
>
>
> I have'nt seen any matrix detailing the capabilities of axiom-woden vs
> axiom-dom4j so I cannot say dropping woden would impact future Axiom
> implementations
> but it does seem like a duplication of effort to support both OM
> implementations
>
> Is there a matrix available to illustrate features and
> functions capabilities of axiom-woden vs axiom-dom4j?
Please note that there is no DOM4J implementation available for
Woden-API it's W3C DOM implementation for Woden-API. Functionality
wise both implementations are more or less same but there is no matrix
available.
Thanks !
> Martin
> ------------------------------------
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte
> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht
> dient lediglich dem Austausch von Informationen und entfaltet keine
> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von
> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
>
>
>
>> Date: Sat, 23 Jun 2012 14:12:38 -0400
>> From: deepalk@gmail.com
>> To: dev@ws.apache.org
>> Subject: Re: [WODEN] Future of Woden Axiom implementation ?
>
>>
>> What is the status of WSDL 2.0 ? how many WS stacks use WSDL 2.0 ?.
>>
>> Deepal
>> > Hi Devs,
>> >
>> > I'm thinking about future of Axiom (OM) based implementation of Woden
>> > API for sometime, whether we should continue or drop support from next
>> > release ?
>> >
>> > AFAIK original objective of OM implementation is to support Axis2 but
>> > in fact Axis2 never used OM implementation instead Axis2 still use DOM
>> > based implementation. Also in my POV there is no such drawbacks with
>> > DOM implementation to move Axis2 to use OM implementation. At the
>> > moment there is no clear indication about users of OM implementation
>> > too. In this situation it is kind of a overhead to maintain OM
>> > implementation further specially with small number of developers. At
>> > the beginning Woden had plans for number of cool features such as
>> > supporting to both WSDL versions etc, but all original developers have
>> > been disappeared from the community few years ago hence it's seem OK
>> > to re-prioritize objectives based on current requirements and
>> > resources.
>> >
>> > This also important decision to reduce complexities among Woden
>> > artifacts, at the moment it's required to have at least 3 JAR files
>> > to use Woden framework as woden-api, woden-impl-common and
>> > woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
>> > merge these artifacts and deliver above 3 module as a single JAR file
>> > called woden.jar. IMO this kind of single artifact deliverables are
>> > more natural for utility projects and easy to deploy on OGSI
>> > containers too.
>> >
>> > Personally I don't have energy to maintain both implementations, also
>> > without actual users no point to maintain OM implementation further.
>> > Based on above facts I would like to suggest terminate OM support from
>> > next release and move forward the project with what ever the useful
>> > features.
>> >
>> > Any thoughts ?
>> >
>> >
>> > Thanks !
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: dev-help@ws.apache.org
>>
--
Sagara Gunathunga
Blog - http://ssagara.blogspot.com
Web - http://people.apache.org/~sagara/
LinkedIn - http://www.linkedin.com/in/ssagara
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
RE: [WODEN] Future of Woden Axiom implementation ?
Posted by Martin Gainty <mg...@hotmail.com>.
Ive have extensively implemented DOM4j based Axiom specifically: <groupId>org.apache.ws.commons.axiom</groupId>
<artifactId>axiom</artifactId>
<name>Axiom</name>
<version>1.2.9-SNAPSHOT</version> I have'nt seen any matrix detailing the capabilities of axiom-woden vs axiom-dom4j so I cannot say dropping woden would impact future Axiom implementationsbut it does seem like a duplication of effort to support both OM implementations Is there a matrix available to illustrate features and functions capabilities of axiom-woden vs axiom-dom4j?Martin------------------------------------
Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen.
> Date: Sat, 23 Jun 2012 14:12:38 -0400
> From: deepalk@gmail.com
> To: dev@ws.apache.org
> Subject: Re: [WODEN] Future of Woden Axiom implementation ?
>
> What is the status of WSDL 2.0 ? how many WS stacks use WSDL 2.0 ?.
>
> Deepal
> > Hi Devs,
> >
> > I'm thinking about future of Axiom (OM) based implementation of Woden
> > API for sometime, whether we should continue or drop support from next
> > release ?
> >
> > AFAIK original objective of OM implementation is to support Axis2 but
> > in fact Axis2 never used OM implementation instead Axis2 still use DOM
> > based implementation. Also in my POV there is no such drawbacks with
> > DOM implementation to move Axis2 to use OM implementation. At the
> > moment there is no clear indication about users of OM implementation
> > too. In this situation it is kind of a overhead to maintain OM
> > implementation further specially with small number of developers. At
> > the beginning Woden had plans for number of cool features such as
> > supporting to both WSDL versions etc, but all original developers have
> > been disappeared from the community few years ago hence it's seem OK
> > to re-prioritize objectives based on current requirements and
> > resources.
> >
> > This also important decision to reduce complexities among Woden
> > artifacts, at the moment it's required to have at least 3 JAR files
> > to use Woden framework as woden-api, woden-impl-common and
> > woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
> > merge these artifacts and deliver above 3 module as a single JAR file
> > called woden.jar. IMO this kind of single artifact deliverables are
> > more natural for utility projects and easy to deploy on OGSI
> > containers too.
> >
> > Personally I don't have energy to maintain both implementations, also
> > without actual users no point to maintain OM implementation further.
> > Based on above facts I would like to suggest terminate OM support from
> > next release and move forward the project with what ever the useful
> > features.
> >
> > Any thoughts ?
> >
> >
> > Thanks !
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: dev-help@ws.apache.org
>
Re: [WODEN] Future of Woden Axiom implementation ?
Posted by Deepal jayasinghe <de...@gmail.com>.
What is the status of WSDL 2.0 ? how many WS stacks use WSDL 2.0 ?.
Deepal
> Hi Devs,
>
> I'm thinking about future of Axiom (OM) based implementation of Woden
> API for sometime, whether we should continue or drop support from next
> release ?
>
> AFAIK original objective of OM implementation is to support Axis2 but
> in fact Axis2 never used OM implementation instead Axis2 still use DOM
> based implementation. Also in my POV there is no such drawbacks with
> DOM implementation to move Axis2 to use OM implementation. At the
> moment there is no clear indication about users of OM implementation
> too. In this situation it is kind of a overhead to maintain OM
> implementation further specially with small number of developers. At
> the beginning Woden had plans for number of cool features such as
> supporting to both WSDL versions etc, but all original developers have
> been disappeared from the community few years ago hence it's seem OK
> to re-prioritize objectives based on current requirements and
> resources.
>
> This also important decision to reduce complexities among Woden
> artifacts, at the moment it's required to have at least 3 JAR files
> to use Woden framework as woden-api, woden-impl-common and
> woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
> merge these artifacts and deliver above 3 module as a single JAR file
> called woden.jar. IMO this kind of single artifact deliverables are
> more natural for utility projects and easy to deploy on OGSI
> containers too.
>
> Personally I don't have energy to maintain both implementations, also
> without actual users no point to maintain OM implementation further.
> Based on above facts I would like to suggest terminate OM support from
> next release and move forward the project with what ever the useful
> features.
>
> Any thoughts ?
>
>
> Thanks !
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org
Re: [WODEN] Future of Woden Axiom implementation ?
Posted by Daniel Kulp <dk...@apache.org>.
I'm certainly OK with this as it seems to make a lot of sense to me. That
said, not being a Woden user or anything, I'm not sure how many people use
Woden. You may want to post a note to the users@ list as a quick poll to
say "we're thinking of doing XYZ, how badly would you be affected" or
something to see if any users would be overly concerned. I'm not saying we
shouldn't do it if there ARE users, but it would at least be a data point to
consider. If the only real "user" of Woden is Axis2, that's another good
thing to know.
Dan
On Saturday, June 23, 2012 09:25:15 PM Sagara Gunathunga wrote:
> Hi Devs,
>
> I'm thinking about future of Axiom (OM) based implementation of Woden
> API for sometime, whether we should continue or drop support from next
> release ?
>
> AFAIK original objective of OM implementation is to support Axis2 but
> in fact Axis2 never used OM implementation instead Axis2 still use DOM
> based implementation. Also in my POV there is no such drawbacks with
> DOM implementation to move Axis2 to use OM implementation. At the
> moment there is no clear indication about users of OM implementation
> too. In this situation it is kind of a overhead to maintain OM
> implementation further specially with small number of developers. At
> the beginning Woden had plans for number of cool features such as
> supporting to both WSDL versions etc, but all original developers have
> been disappeared from the community few years ago hence it's seem OK
> to re-prioritize objectives based on current requirements and
> resources.
>
> This also important decision to reduce complexities among Woden
> artifacts, at the moment it's required to have at least 3 JAR files
> to use Woden framework as woden-api, woden-impl-common and
> woden-impl-dom/woden-impl-om. Dropping OM implementation allows to
> merge these artifacts and deliver above 3 module as a single JAR file
> called woden.jar. IMO this kind of single artifact deliverables are
> more natural for utility projects and easy to deploy on OGSI
> containers too.
>
> Personally I don't have energy to maintain both implementations, also
> without actual users no point to maintain OM implementation further.
> Based on above facts I would like to suggest terminate OM support from
> next release and move forward the project with what ever the useful
> features.
>
> Any thoughts ?
>
>
> Thanks !
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@ws.apache.org
For additional commands, e-mail: dev-help@ws.apache.org