axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Fremantle" <pzf...@gmail.com>
Subject Fwd: [Axis2] Moving all the transports into a common modules
Date Thu, 02 Oct 2008 13:42:33 GMT
Apologies for reposting I forgot to reply-all.

Paul
---------- Forwarded message ----------
From: Paul Fremantle <pzfreo@gmail.com>
Date: Thu, Oct 2, 2008 at 2:41 PM
Subject: Re: [Axis2] Moving all the transports into a common modules
To: dev@synapse.apache.org


Deepal

There is a problem :)

The JMS transport is completely different. So we can't take the
Synapse JMS transport and give it the name of the different (old)
Axis2 transport.

The second problem is that (suppose) Synapse would like to do a
release before the next Axis2 release. Because the old transports are
still in the Axis2 core, we cannot ship the updated Commons
Transports.

Also, the transports are only named in axis2.xml right? I don't think
there are backwards compatibility issues. We have never (afaik)
maintained full compatibility for axis2.xml.

I think we should rename these.

Paul

On Mon, Sep 22, 2008 at 1:53 PM, Deepal jayasinghe <deepalk@gmail.com> wrote:
> Amila Suriarachchi wrote:
>> hi,
>> the package name that commons transport module use is org.apache.axis2
>>
>> I think it should be org.apache.ws.commons
> No Amila , we can not do that for transport like HTTP , that would be a
> major  change and backward compatibility killer. So lets keep the
> package name as it is.
>
> [Please do not change the package names  :) ]
> -Deepal
>>
>> WDYT?
>>
>> thanks,
>> Amila.
>>
>> On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
>> <amilasuriarachchi@gmail.com <mailto:amilasuriarachchi@gmail.com>> wrote:
>>
>>
>>
>>     On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>     <andreas.veithen@skynet.be <mailto:andreas.veithen@skynet.be>> wrote:
>>
>>         Deepal,
>>
>>         Before we can move anything from Synapse to the new commons
>>         module, we need to decide which transports we move (all or
>>         only a subset) and based on that, we need to make sure that
>>         all the people involved in the maintenance of these transports
>>         have commit access to the new module.
>>
>>
>>     As a starting point I'll put the synapse SMTP transport to commons
>>     transport and try to test with Axis2.
>>
>>     thanks,
>>     Amila.
>>
>>
>>
>>         In the meantime, I also have two comments/questions related to
>>         the code that is already in the new module:
>>         1. Wouldn't it be a good idea to take advantage of the move
>>         from Axis2 to ws-commons to use a more conventional directory
>>         structure, e.g. src/main/java instead of src?
>>         2. I don't see any documentation in the new module. There must
>>         have been some docs for the transports in Axis2. When will
>>         this be moved?
>>
>>         Regards,
>>
>>         Andreas
>>
>>
>>         On 21 sept. 08, at 03:13, Deepal jayasinghe wrote:
>>
>>             Hi all,
>>
>>             Few months back we all agreed to move all commons
>>             transports (from Axis2
>>             and Synapse) to a common module. As  the first step of
>>             that I have moved
>>             all the Axis2 to transport into a common module in
>>             ws-commons [1]. In
>>             addition to that we have setup nightly builds from that
>>             modules. So now
>>             its time for Synapse dev to move their transports into
>>             that module :)
>>
>>             [1] :
>>             https://svn.apache.org/repos/asf/webservices/commons/trunk/modules/transport
>>
>>             Thank you!
>>             Deepal
>>
>>             --
>>             Thank you!
>>
>>
>>             http://blogs.deepal.org
>>
>>
>>             ---------------------------------------------------------------------
>>             To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>             <mailto:axis-dev-unsubscribe@ws.apache.org>
>>             For additional commands, e-mail:
>>             axis-dev-help@ws.apache.org
>>             <mailto:axis-dev-help@ws.apache.org>
>>
>>
>>
>>         ---------------------------------------------------------------------
>>         To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>         <mailto:axis-dev-unsubscribe@ws.apache.org>
>>         For additional commands, e-mail: axis-dev-help@ws.apache.org
>>         <mailto:axis-dev-help@ws.apache.org>
>>
>>
>>
>>
>>     --
>>     Amila Suriarachchi
>>     WSO2 Inc.
>>     blog: http://amilachinthaka.blogspot.com/
>>
>>
>>
>>
>> --
>> Amila Suriarachchi
>> WSO2 Inc.
>> blog: http://amilachinthaka.blogspot.com/
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>



--
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com



-- 
Paul Fremantle
Co-Founder and CTO, WSO2
Apache Synapse PMC Chair
OASIS WS-RX TC Co-chair

blog: http://pzf.fremantle.org
paul@wso2.com

"Oxygenating the Web Service Platform", www.wso2.com

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


Mime
View raw message