You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Deepal jayasinghe <de...@gmail.com> on 2008/09/21 03:13:38 UTC
[Axis2] Moving all the transports into a common modules
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
> 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.
+1
>
> 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?
It does not matter I guess , src/main/java is the default folder
structure of maven2. That does not mean we need to have exactly same
structure for our project. We can have any kind of src file structure
and configure pom.xml accordingly. Which approach you use , there will
not be any changes in the generated project or the generated jar files.
> 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?
Hmm , I think all those documents are about how to configure different
transports in Axis2. So I think those belong to Axis2 not to transports
module.
-Deepal
>
> 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
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
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
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
> 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.
+1
>
> 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?
It does not matter I guess , src/main/java is the default folder
structure of maven2. That does not mean we need to have exactly same
structure for our project. We can have any kind of src file structure
and configure pom.xml accordingly. Which approach you use , there will
not be any changes in the generated project or the generated jar files.
> 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?
Hmm , I think all those documents are about how to configure different
transports in Axis2. So I think those belong to Axis2 not to transports
module.
-Deepal
>
> 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
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Thank you!
http://blogs.deepal.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
Hi Paul and all,
> 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.
>
That is fine , because JMS is not a commonly used transport in Axis2 , I
mean most of the people use HTTP. So I have no issue with giving any
kind of package name for JMS 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.
>
Nope , all the transports codes are in commons (except Axis2 related
transports and utilities , which we are not going move anyway)
> Also, the transports are only named in axis2.xml right? I don't think
> there are backwards compatibility issues.
The problem is when we add a transport we add the full qualified package
name , so then there is a problem. Meaning if someone need to upgrade
into next version of Axis2 then he has to change axis2.xml again , not
only that there may be instances where the generated code does not work
as well.
> We have never (afaik)
> maintained full compatibility for axis2.xml.
>
Well , I do not agree here , we did not do any major changes after 1.1
release (in fact I always -1 for those changes ;-) ). We stop doing
major package rename and interface changes.
So I can not understand why we need to the change the package name of
the transports. There is no hard and fast rule saying that the package
name of all the classes are in ws-commons has to be like that and this .
IMO changing package name is not that something we really need ,it just
nice to have. So , its better to think about the backward compatibility
than nice to have features. :-)
Thank you!
Deepal
> I think we should rename these.
>
> Paul
>
> On Mon, Sep 22, 2008 at 1:53 PM, Deepal jayasinghe <de...@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 <ma...@gmail.com>> wrote:
>>>
>>>
>>>
>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>> <andreas.veithen@skynet.be <ma...@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
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail:
>>> axis-dev-help@ws.apache.org
>>> <ma...@ws.apache.org>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>> <ma...@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
>>
>>
>>
>
>
>
>
--
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
Re: Fwd: [Axis2] Moving all the transports into a common modules
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+1 - given that these are set in axis2.xml I see no issue in changing the
package names.
Sanjiva.
Paul Fremantle wrote:
> Apologies for reposting I forgot to reply-all.
>
> Paul
> ---------- Forwarded message ----------
> From: Paul Fremantle <pz...@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 <de...@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 <ma...@gmail.com>> wrote:
>>>
>>>
>>>
>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>> <andreas.veithen@skynet.be <ma...@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
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail:
>>> axis-dev-help@ws.apache.org
>>> <ma...@ws.apache.org>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>> <ma...@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
>
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
Blog: http://sanjiva.weerawarana.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: Fwd: [Axis2] Moving all the transports into a common modules
Posted by Sanjiva Weerawarana <sa...@opensource.lk>.
+1 - given that these are set in axis2.xml I see no issue in changing the
package names.
Sanjiva.
Paul Fremantle wrote:
> Apologies for reposting I forgot to reply-all.
>
> Paul
> ---------- Forwarded message ----------
> From: Paul Fremantle <pz...@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 <de...@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 <ma...@gmail.com>> wrote:
>>>
>>>
>>>
>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>> <andreas.veithen@skynet.be <ma...@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
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail:
>>> axis-dev-help@ws.apache.org
>>> <ma...@ws.apache.org>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>> <ma...@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
>
>
>
--
Sanjiva Weerawarana, Ph.D.
Founder & Director; Lanka Software Foundation; http://www.opensource.lk/
Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/
Member; Apache Software Foundation; http://www.apache.org/
Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/
Blog: http://sanjiva.weerawarana.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Fwd: [Axis2] Moving all the transports into a common modules
Posted by Paul Fremantle <pz...@gmail.com>.
Apologies for reposting I forgot to reply-all.
Paul
---------- Forwarded message ----------
From: Paul Fremantle <pz...@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 <de...@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 <ma...@gmail.com>> wrote:
>>
>>
>>
>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>> <andreas.veithen@skynet.be <ma...@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
>> <ma...@ws.apache.org>
>> For additional commands, e-mail:
>> axis-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>> <ma...@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
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
> +1 I dont see any issues in renaming the packages too.
:) , the issue is backward compatibility , which is an issues for me :)
.The reason is doing major changes to a project like Axis2 in this stage
is not a good idea.
-Deepal
>
> Thanks,
> Keith.
>
> On Thu, Oct 2, 2008 at 7:11 PM, Paul Fremantle <pzfreo@gmail.com
> <ma...@gmail.com>> wrote:
>
> 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 <ma...@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
> <ma...@gmail.com>
> <mailto:amilasuriarachchi@gmail.com
> <ma...@gmail.com>>> wrote:
> >>
> >>
> >>
> >> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> >> <andreas.veithen@skynet.be
> <ma...@skynet.be>
> <mailto:andreas.veithen@skynet.be
> <ma...@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
> <ma...@ws.apache.org>
> >> <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> >> For additional commands, e-mail:
> >> axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> >> <mailto:axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> >>
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> >> <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> >> For additional commands, e-mail:
> axis-dev-help@ws.apache.org <ma...@ws.apache.org>
> >> <mailto:axis-dev-help@ws.apache.org
> <ma...@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
> <ma...@synapse.apache.org>
> > For additional commands, e-mail: dev-help@synapse.apache.org
> <ma...@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 <ma...@wso2.com>
>
> "Oxygenating the Web Service Platform", www.wso2.com
> <http://www.wso2.com>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> <ma...@synapse.apache.org>
> For additional commands, e-mail: dev-help@synapse.apache.org
> <ma...@synapse.apache.org>
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
--
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
Re: [Axis2] Moving all the transports into a common modules
Posted by keith chapman <ke...@gmail.com>.
+1 I dont see any issues in renaming the packages too.
Thanks,
Keith.
On Thu, Oct 2, 2008 at 7:11 PM, Paul Fremantle <pz...@gmail.com> wrote:
> 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 <de...@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 <ma...@gmail.com>>
> wrote:
> >>
> >>
> >>
> >> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> >> <andreas.veithen@skynet.be <ma...@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
> >> <ma...@ws.apache.org>
> >> For additional commands, e-mail:
> >> axis-dev-help@ws.apache.org
> >> <ma...@ws.apache.org>
> >>
> >>
> >>
> >>
> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> >> <ma...@ws.apache.org>
> >> For additional commands, e-mail: axis-dev-help@ws.apache.org
> >> <ma...@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
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Fwd: [Axis2] Moving all the transports into a common modules
Posted by Paul Fremantle <pz...@gmail.com>.
Apologies for reposting I forgot to reply-all.
Paul
---------- Forwarded message ----------
From: Paul Fremantle <pz...@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 <de...@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 <ma...@gmail.com>> wrote:
>>
>>
>>
>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>> <andreas.veithen@skynet.be <ma...@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
>> <ma...@ws.apache.org>
>> For additional commands, e-mail:
>> axis-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>> <ma...@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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Ruwan Linton <ru...@gmail.com>.
Andreas,
There doesn't seem to be a soon Axis2 release, but from my point of view
synapse community might want a release with an existing axis2 release....
Probably 1.4.1 before going for the next version of axis2 in which case we
need to back down to the axis2-1.4.1 release, which is OK.
Thanks,
Ruwan
On Thu, Oct 2, 2008 at 9:47 PM, Andreas Veithen
<an...@skynet.be>wrote:
> Paul,
>
> Currently Synapse trunk depends on the snapshot version of Axis2.
> Logically, this means that we will only release a new version of Synapse
> after the next release of Axis2 (or alternatively release a Synapse version
> depending on an Axis2 snapshot). If you consider the possibility of a
> Synapse release based on Axis2 1.4 (or 1.4.1), then as a consequence we
> should change the dependencies of Synapse trunk.
>
> Andreas
>
>
> Paul Fremantle wrote:
>
>> 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 <de...@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 <ma...@gmail.com>>
>>>> wrote:
>>>>
>>>>
>>>>
>>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>>> <andreas.veithen@skynet.be <ma...@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
>>>> <ma...@ws.apache.org>
>>>> For additional commands, e-mail:
>>>> axis-dev-help@ws.apache.org
>>>> <ma...@ws.apache.org>
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>>> <ma...@ws.apache.org>
>>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>>> <ma...@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
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by Ruwan Linton <ru...@gmail.com>.
Andreas,
There doesn't seem to be a soon Axis2 release, but from my point of view
synapse community might want a release with an existing axis2 release....
Probably 1.4.1 before going for the next version of axis2 in which case we
need to back down to the axis2-1.4.1 release, which is OK.
Thanks,
Ruwan
On Thu, Oct 2, 2008 at 9:47 PM, Andreas Veithen
<an...@skynet.be>wrote:
> Paul,
>
> Currently Synapse trunk depends on the snapshot version of Axis2.
> Logically, this means that we will only release a new version of Synapse
> after the next release of Axis2 (or alternatively release a Synapse version
> depending on an Axis2 snapshot). If you consider the possibility of a
> Synapse release based on Axis2 1.4 (or 1.4.1), then as a consequence we
> should change the dependencies of Synapse trunk.
>
> Andreas
>
>
> Paul Fremantle wrote:
>
>> 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 <de...@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 <ma...@gmail.com>>
>>>> wrote:
>>>>
>>>>
>>>>
>>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>>> <andreas.veithen@skynet.be <ma...@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
>>>> <ma...@ws.apache.org>
>>>> For additional commands, e-mail:
>>>> axis-dev-help@ws.apache.org
>>>> <ma...@ws.apache.org>
>>>>
>>>>
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>>> <ma...@ws.apache.org>
>>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>>> <ma...@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
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
Paul,
Currently Synapse trunk depends on the snapshot version of Axis2.
Logically, this means that we will only release a new version of Synapse
after the next release of Axis2 (or alternatively release a Synapse
version depending on an Axis2 snapshot). If you consider the possibility
of a Synapse release based on Axis2 1.4 (or 1.4.1), then as a
consequence we should change the dependencies of Synapse trunk.
Andreas
Paul Fremantle wrote:
> 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 <de...@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 <ma...@gmail.com>> wrote:
>>>
>>>
>>>
>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>> <andreas.veithen@skynet.be <ma...@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
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail:
>>> axis-dev-help@ws.apache.org
>>> <ma...@ws.apache.org>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>> <ma...@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
>>
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
Paul,
Currently Synapse trunk depends on the snapshot version of Axis2.
Logically, this means that we will only release a new version of Synapse
after the next release of Axis2 (or alternatively release a Synapse
version depending on an Axis2 snapshot). If you consider the possibility
of a Synapse release based on Axis2 1.4 (or 1.4.1), then as a
consequence we should change the dependencies of Synapse trunk.
Andreas
Paul Fremantle wrote:
> 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 <de...@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 <ma...@gmail.com>> wrote:
>>>
>>>
>>>
>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>> <andreas.veithen@skynet.be <ma...@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
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail:
>>> axis-dev-help@ws.apache.org
>>> <ma...@ws.apache.org>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>> <ma...@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
>>
>>
>>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
Hi Paul and all,
> 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.
>
That is fine , because JMS is not a commonly used transport in Axis2 , I
mean most of the people use HTTP. So I have no issue with giving any
kind of package name for JMS 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.
>
Nope , all the transports codes are in commons (except Axis2 related
transports and utilities , which we are not going move anyway)
> Also, the transports are only named in axis2.xml right? I don't think
> there are backwards compatibility issues.
The problem is when we add a transport we add the full qualified package
name , so then there is a problem. Meaning if someone need to upgrade
into next version of Axis2 then he has to change axis2.xml again , not
only that there may be instances where the generated code does not work
as well.
> We have never (afaik)
> maintained full compatibility for axis2.xml.
>
Well , I do not agree here , we did not do any major changes after 1.1
release (in fact I always -1 for those changes ;-) ). We stop doing
major package rename and interface changes.
So I can not understand why we need to the change the package name of
the transports. There is no hard and fast rule saying that the package
name of all the classes are in ws-commons has to be like that and this .
IMO changing package name is not that something we really need ,it just
nice to have. So , its better to think about the backward compatibility
than nice to have features. :-)
Thank you!
Deepal
> I think we should rename these.
>
> Paul
>
> On Mon, Sep 22, 2008 at 1:53 PM, Deepal jayasinghe <de...@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 <ma...@gmail.com>> wrote:
>>>
>>>
>>>
>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>> <andreas.veithen@skynet.be <ma...@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
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail:
>>> axis-dev-help@ws.apache.org
>>> <ma...@ws.apache.org>
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>>> <ma...@ws.apache.org>
>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>> <ma...@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
>>
>>
>>
>
>
>
>
--
Thank you!
http://blogs.deepal.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Paul Fremantle <pz...@gmail.com>.
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 <de...@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 <ma...@gmail.com>> wrote:
>>
>>
>>
>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>> <andreas.veithen@skynet.be <ma...@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
>> <ma...@ws.apache.org>
>> For additional commands, e-mail:
>> axis-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>> <ma...@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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
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 <ma...@gmail.com>> wrote:
>
>
>
> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> <andreas.veithen@skynet.be <ma...@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
> <ma...@ws.apache.org>
> For additional commands, e-mail:
> axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@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
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
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 <ma...@gmail.com>> wrote:
>
>
>
> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> <andreas.veithen@skynet.be <ma...@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
> <ma...@ws.apache.org>
> For additional commands, e-mail:
> axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Ruwan Linton <ru...@gmail.com>.
Well, you are correct andreas, but the real problem is if we (synapse) want
to go for a release with an existing axis2 release in which case there will
be two classes having the name org.apache.axis2.transports.jms.JMSSender
even though we worked around the backward compatibility of axis2.xml
Do we want to hack that up as well. If we want to, I have a number of
solutions ;-)
Thanks,
Ruwan
On Thu, Oct 2, 2008 at 10:18 PM, Andreas Veithen
<an...@skynet.be>wrote:
> We can easily guarantee backward compatibility (for axis2.xml) by having a
> set of classes with the old package names and extending the corresponding
> classes in the new version. Since this is only needed for transport
> listeners/senders and message formatters/builders, it would not require too
> much effort.
>
> Andreas
>
> Ruwan Linton wrote:
>
>> Hi Deepal,
>>
>> Synapse also has the same backward compatibility issue that you are
>> talking about with the axis2.xml that synapse ships with, therefore shall we
>> keep the transports that synapse community contributed as it is
>> (org.apache.synapse.transports) ;-)
>>
>> Thanks,
>> Ruwan
>>
>> On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe <deepalk@gmail.com<mailto:
>> deepalk@gmail.com>> wrote:
>>
>>
>> > hi,
>> > the package name that commons transport module use is
>> org.apache.axis2
>> >
>> > I think it should be org.apache.ws.commons
>> Saying no one more time :)
>>
>> I do not think that all the modules in commons should have the package
>> name org.apache.ws.commons , as an example have a look at Axiom
>> and Neethi
>>
>> org.apache.neethi
>> org.apache.axiom
>>
>> So IMO it is ok to have axis2 transport package name as it is :)
>>
>> -Deepal
>> >
>> > WDYT?
>> >
>> > thanks,
>> > Amila.
>> >
>> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
>> > <amilasuriarachchi@gmail.com
>> <ma...@gmail.com>
>> <mailto:amilasuriarachchi@gmail.com
>>
>> <ma...@gmail.com>>> wrote:
>> >
>> >
>> >
>> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>> > <andreas.veithen@skynet.be
>> <ma...@skynet.be>
>> <mailto:andreas.veithen@skynet.be
>> <ma...@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
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> > For additional commands, e-mail:
>> > axis-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>> >
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> > For additional commands, e-mail:
>> axis-dev-help@ws.apache.org <ma...@ws.apache.org>
>> > <mailto:axis-dev-help@ws.apache.org
>> <ma...@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
>> <ma...@synapse.apache.org>
>> For additional commands, e-mail: dev-help@synapse.apache.org
>> <ma...@synapse.apache.org>
>>
>>
>>
>>
>> --
>> Ruwan Linton
>> http://wso2.org - "Oxygenating the Web Services Platform"
>> http://ruwansblog.blogspot.com/
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by Ruwan Linton <ru...@gmail.com>.
Well, you are correct andreas, but the real problem is if we (synapse) want
to go for a release with an existing axis2 release in which case there will
be two classes having the name org.apache.axis2.transports.jms.JMSSender
even though we worked around the backward compatibility of axis2.xml
Do we want to hack that up as well. If we want to, I have a number of
solutions ;-)
Thanks,
Ruwan
On Thu, Oct 2, 2008 at 10:18 PM, Andreas Veithen
<an...@skynet.be>wrote:
> We can easily guarantee backward compatibility (for axis2.xml) by having a
> set of classes with the old package names and extending the corresponding
> classes in the new version. Since this is only needed for transport
> listeners/senders and message formatters/builders, it would not require too
> much effort.
>
> Andreas
>
> Ruwan Linton wrote:
>
>> Hi Deepal,
>>
>> Synapse also has the same backward compatibility issue that you are
>> talking about with the axis2.xml that synapse ships with, therefore shall we
>> keep the transports that synapse community contributed as it is
>> (org.apache.synapse.transports) ;-)
>>
>> Thanks,
>> Ruwan
>>
>> On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe <deepalk@gmail.com<mailto:
>> deepalk@gmail.com>> wrote:
>>
>>
>> > hi,
>> > the package name that commons transport module use is
>> org.apache.axis2
>> >
>> > I think it should be org.apache.ws.commons
>> Saying no one more time :)
>>
>> I do not think that all the modules in commons should have the package
>> name org.apache.ws.commons , as an example have a look at Axiom
>> and Neethi
>>
>> org.apache.neethi
>> org.apache.axiom
>>
>> So IMO it is ok to have axis2 transport package name as it is :)
>>
>> -Deepal
>> >
>> > WDYT?
>> >
>> > thanks,
>> > Amila.
>> >
>> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
>> > <amilasuriarachchi@gmail.com
>> <ma...@gmail.com>
>> <mailto:amilasuriarachchi@gmail.com
>>
>> <ma...@gmail.com>>> wrote:
>> >
>> >
>> >
>> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>> > <andreas.veithen@skynet.be
>> <ma...@skynet.be>
>> <mailto:andreas.veithen@skynet.be
>> <ma...@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
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> > For additional commands, e-mail:
>> > axis-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>> >
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> > For additional commands, e-mail:
>> axis-dev-help@ws.apache.org <ma...@ws.apache.org>
>> > <mailto:axis-dev-help@ws.apache.org
>> <ma...@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
>> <ma...@synapse.apache.org>
>> For additional commands, e-mail: dev-help@synapse.apache.org
>> <ma...@synapse.apache.org>
>>
>>
>>
>>
>> --
>> Ruwan Linton
>> http://wso2.org - "Oxygenating the Web Services Platform"
>> http://ruwansblog.blogspot.com/
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
We can easily guarantee backward compatibility (for axis2.xml) by having
a set of classes with the old package names and extending the
corresponding classes in the new version. Since this is only needed for
transport listeners/senders and message formatters/builders, it would
not require too much effort.
Andreas
Ruwan Linton wrote:
> Hi Deepal,
>
> Synapse also has the same backward compatibility issue that you are
> talking about with the axis2.xml that synapse ships with, therefore
> shall we keep the transports that synapse community contributed as it
> is (org.apache.synapse.transports) ;-)
>
> Thanks,
> Ruwan
>
> On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe <deepalk@gmail.com
> <ma...@gmail.com>> wrote:
>
>
> > hi,
> > the package name that commons transport module use is
> org.apache.axis2
> >
> > I think it should be org.apache.ws.commons
> Saying no one more time :)
>
> I do not think that all the modules in commons should have the package
> name org.apache.ws.commons , as an example have a look at Axiom
> and Neethi
>
> org.apache.neethi
> org.apache.axiom
>
> So IMO it is ok to have axis2 transport package name as it is :)
>
> -Deepal
> >
> > WDYT?
> >
> > thanks,
> > Amila.
> >
> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
> > <amilasuriarachchi@gmail.com
> <ma...@gmail.com>
> <mailto:amilasuriarachchi@gmail.com
> <ma...@gmail.com>>> wrote:
> >
> >
> >
> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> > <andreas.veithen@skynet.be
> <ma...@skynet.be>
> <mailto:andreas.veithen@skynet.be
> <ma...@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
> <ma...@ws.apache.org>
> > <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> > For additional commands, e-mail:
> > axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> > <mailto:axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> > <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> > For additional commands, e-mail:
> axis-dev-help@ws.apache.org <ma...@ws.apache.org>
> > <mailto:axis-dev-help@ws.apache.org
> <ma...@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
> <ma...@synapse.apache.org>
> For additional commands, e-mail: dev-help@synapse.apache.org
> <ma...@synapse.apache.org>
>
>
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
Ruwan Linton wrote:
> Hi Deepal,
>
> Synapse also has the same backward compatibility issue that you are
> talking about with the axis2.xml that synapse ships with, therefore
> shall we keep the transports that synapse community contributed as it
> is (org.apache.synapse.transports) ;-)
>
yes of course . :-) , in fact you should.
-Deepal
> Thanks,
> Ruwan
>
> On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe <deepalk@gmail.com
> <ma...@gmail.com>> wrote:
>
>
> > hi,
> > the package name that commons transport module use is
> org.apache.axis2
> >
> > I think it should be org.apache.ws.commons
> Saying no one more time :)
>
> I do not think that all the modules in commons should have the package
> name org.apache.ws.commons , as an example have a look at Axiom
> and Neethi
>
> org.apache.neethi
> org.apache.axiom
>
> So IMO it is ok to have axis2 transport package name as it is :)
>
> -Deepal
> >
> > WDYT?
> >
> > thanks,
> > Amila.
> >
> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
> > <amilasuriarachchi@gmail.com
> <ma...@gmail.com>
> <mailto:amilasuriarachchi@gmail.com
> <ma...@gmail.com>>> wrote:
> >
> >
> >
> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> > <andreas.veithen@skynet.be
> <ma...@skynet.be>
> <mailto:andreas.veithen@skynet.be
> <ma...@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
> <ma...@ws.apache.org>
> > <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> > For additional commands, e-mail:
> > axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> > <mailto:axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> > <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> > For additional commands, e-mail:
> axis-dev-help@ws.apache.org <ma...@ws.apache.org>
> > <mailto:axis-dev-help@ws.apache.org
> <ma...@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
> <ma...@synapse.apache.org>
> For additional commands, e-mail: dev-help@synapse.apache.org
> <ma...@synapse.apache.org>
>
>
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
--
Thank you!
http://blogs.deepal.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Paul Fremantle <pz...@gmail.com>.
Andreas
> I didn't express my idea clearly. What I meant was that in my proposal, only
> the transports coming from Synapse will have new package names, so there is
> no impact on the Axis2 community in general and the package renames will
> only be a concern for Synapse.
My only concern is that this is meant to be unifying the transports.
The history of this was that we somehow ended up with two sets of
transports instead of just one. I think it would be a big shame to end
up with one set of transports, finally, but have the package names
somehow continue to propagate the old view and old disjoint structure.
That is why I really liked your delegate proposal. In fact I
personally wouldn't put the delegates into Synapse. I don't think
Synapse users are really using the Axis2 transports and I think most
of them can handle changing the axis2.xml. I would save the delegates
for the Axis2 1.5 release when there are no more transports in the
core Axis2 build.
Paul
PS Sorry everyone to cause such fun over what I thought was simple :)
Maybe we should have spent the hours on hacking towards an Axis2 1.5
release instead :)
--
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: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Paul Fremantle <pz...@gmail.com>.
Andreas
> I didn't express my idea clearly. What I meant was that in my proposal, only
> the transports coming from Synapse will have new package names, so there is
> no impact on the Axis2 community in general and the package renames will
> only be a concern for Synapse.
My only concern is that this is meant to be unifying the transports.
The history of this was that we somehow ended up with two sets of
transports instead of just one. I think it would be a big shame to end
up with one set of transports, finally, but have the package names
somehow continue to propagate the old view and old disjoint structure.
That is why I really liked your delegate proposal. In fact I
personally wouldn't put the delegates into Synapse. I don't think
Synapse users are really using the Axis2 transports and I think most
of them can handle changing the axis2.xml. I would save the delegates
for the Axis2 1.5 release when there are no more transports in the
core Axis2 build.
Paul
PS Sorry everyone to cause such fun over what I thought was simple :)
Maybe we should have spent the hours on hacking towards an Axis2 1.5
release instead :)
--
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
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
On 2 oct. 08, at 23:45, Deepal jayasinghe wrote:
>
>> I'm happy with Paul's proposal. However there is also another
>> alternative:
>>
>> 1) Keep the org.apache.axis2.transport package name for all
>> transports
>> (as it is now in trunk).
>> 2) Before creating the first release of the new transports (and
>> therefore also before the next Synapse release; see point 3), we
>> create a new Axis2 release 1.4.2, which will basically be 1.4.1 minus
>> the old transports. Of course the persons volunteering to create that
>> release may decide to include other critical fixes.
>> 3) The next Synapse release will depend on Axis2 1.4.2 and the first
>> release of the new transports.
>> 4) In Synapse we implement the compatibility classes I suggested so
>> that we maintain compatibility at the axis2.xml level (at least for
>> one release cycle).
>>
> +1
>> Advantages:
>> * We have a common package name (not a mix of org.apache.axis2 and
>> org.apache.synapse) that is the same as the original one (before the
>> Synapse transports were created).
> Well you are right , those are Axis2 transports I mean implement Axis2
> transports interfaces so having o.a.axis2 is more meaning full. I mean
> those transport can not be used without Axis2.(Even in synapse it uses
> Axis2)
>> * Users of the transports (other than HTTP) have a better migration
>> path from Axis2 1.4.1 to Axis2 1.5. Indeed, the fact that the JMS and
>> mail transports are quite different from the old Axis2 versions will
>> make it necessary for them to retest (and maybe rework) their
>> application. If they can do that independently from the other changes
>> in Axis2 1.5, it will probably make things easier for them.
> +1
>> * The compatibility problem caused by the package renames is only a
>> concern for Synapse, not for the whole Axis2 community.
> My concern was Axis2 in general.
I didn't express my idea clearly. What I meant was that in my
proposal, only the transports coming from Synapse will have new
package names, so there is no impact on the Axis2 community in general
and the package renames will only be a concern for Synapse.
>
>> * Assuming that people from Synapse participate in the creation of
>> the
>> 1.4.2 release and do the work, we could include some fixes that are
>> critical to Synapse.
>>
>> Disadvantage:
>> * We can't change the dependency of Synapse trunk to 1.4.2 now,
>> because this release doesn't exist yet.
> Yes I agree , for that let's try to do 1.4.2 release as soon as we
> can.
>
There is an additional benefit when releasing 1.4.2 soon: it would
allow us to create the first release of the transports sooner, which
in turn allows us to get more feedback from the community. The
drawback is that we loose the last advantage I mentioned (i.e. that of
using 1.4.2 to get critical fixes for Synapse into Axis2).
> Thank you!
> Deepal
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
On 2 oct. 08, at 23:45, Deepal jayasinghe wrote:
>
>> I'm happy with Paul's proposal. However there is also another
>> alternative:
>>
>> 1) Keep the org.apache.axis2.transport package name for all
>> transports
>> (as it is now in trunk).
>> 2) Before creating the first release of the new transports (and
>> therefore also before the next Synapse release; see point 3), we
>> create a new Axis2 release 1.4.2, which will basically be 1.4.1 minus
>> the old transports. Of course the persons volunteering to create that
>> release may decide to include other critical fixes.
>> 3) The next Synapse release will depend on Axis2 1.4.2 and the first
>> release of the new transports.
>> 4) In Synapse we implement the compatibility classes I suggested so
>> that we maintain compatibility at the axis2.xml level (at least for
>> one release cycle).
>>
> +1
>> Advantages:
>> * We have a common package name (not a mix of org.apache.axis2 and
>> org.apache.synapse) that is the same as the original one (before the
>> Synapse transports were created).
> Well you are right , those are Axis2 transports I mean implement Axis2
> transports interfaces so having o.a.axis2 is more meaning full. I mean
> those transport can not be used without Axis2.(Even in synapse it uses
> Axis2)
>> * Users of the transports (other than HTTP) have a better migration
>> path from Axis2 1.4.1 to Axis2 1.5. Indeed, the fact that the JMS and
>> mail transports are quite different from the old Axis2 versions will
>> make it necessary for them to retest (and maybe rework) their
>> application. If they can do that independently from the other changes
>> in Axis2 1.5, it will probably make things easier for them.
> +1
>> * The compatibility problem caused by the package renames is only a
>> concern for Synapse, not for the whole Axis2 community.
> My concern was Axis2 in general.
I didn't express my idea clearly. What I meant was that in my
proposal, only the transports coming from Synapse will have new
package names, so there is no impact on the Axis2 community in general
and the package renames will only be a concern for Synapse.
>
>> * Assuming that people from Synapse participate in the creation of
>> the
>> 1.4.2 release and do the work, we could include some fixes that are
>> critical to Synapse.
>>
>> Disadvantage:
>> * We can't change the dependency of Synapse trunk to 1.4.2 now,
>> because this release doesn't exist yet.
> Yes I agree , for that let's try to do 1.4.2 release as soon as we
> can.
>
There is an additional benefit when releasing 1.4.2 soon: it would
allow us to create the first release of the transports sooner, which
in turn allows us to get more feedback from the community. The
drawback is that we loose the last advantage I mentioned (i.e. that of
using 1.4.2 to get critical fixes for Synapse into Axis2).
> Thank you!
> Deepal
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
> I'm happy with Paul's proposal. However there is also another
> alternative:
>
> 1) Keep the org.apache.axis2.transport package name for all transports
> (as it is now in trunk).
> 2) Before creating the first release of the new transports (and
> therefore also before the next Synapse release; see point 3), we
> create a new Axis2 release 1.4.2, which will basically be 1.4.1 minus
> the old transports. Of course the persons volunteering to create that
> release may decide to include other critical fixes.
> 3) The next Synapse release will depend on Axis2 1.4.2 and the first
> release of the new transports.
> 4) In Synapse we implement the compatibility classes I suggested so
> that we maintain compatibility at the axis2.xml level (at least for
> one release cycle).
>
+1
> Advantages:
> * We have a common package name (not a mix of org.apache.axis2 and
> org.apache.synapse) that is the same as the original one (before the
> Synapse transports were created).
Well you are right , those are Axis2 transports I mean implement Axis2
transports interfaces so having o.a.axis2 is more meaning full. I mean
those transport can not be used without Axis2.(Even in synapse it uses
Axis2)
> * Users of the transports (other than HTTP) have a better migration
> path from Axis2 1.4.1 to Axis2 1.5. Indeed, the fact that the JMS and
> mail transports are quite different from the old Axis2 versions will
> make it necessary for them to retest (and maybe rework) their
> application. If they can do that independently from the other changes
> in Axis2 1.5, it will probably make things easier for them.
+1
> * The compatibility problem caused by the package renames is only a
> concern for Synapse, not for the whole Axis2 community.
My concern was Axis2 in general.
> * Assuming that people from Synapse participate in the creation of the
> 1.4.2 release and do the work, we could include some fixes that are
> critical to Synapse.
>
> Disadvantage:
> * We can't change the dependency of Synapse trunk to 1.4.2 now,
> because this release doesn't exist yet.
Yes I agree , for that let's try to do 1.4.2 release as soon as we can.
Thank you!
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
> I'm happy with Paul's proposal. However there is also another
> alternative:
>
> 1) Keep the org.apache.axis2.transport package name for all transports
> (as it is now in trunk).
> 2) Before creating the first release of the new transports (and
> therefore also before the next Synapse release; see point 3), we
> create a new Axis2 release 1.4.2, which will basically be 1.4.1 minus
> the old transports. Of course the persons volunteering to create that
> release may decide to include other critical fixes.
> 3) The next Synapse release will depend on Axis2 1.4.2 and the first
> release of the new transports.
> 4) In Synapse we implement the compatibility classes I suggested so
> that we maintain compatibility at the axis2.xml level (at least for
> one release cycle).
>
+1
> Advantages:
> * We have a common package name (not a mix of org.apache.axis2 and
> org.apache.synapse) that is the same as the original one (before the
> Synapse transports were created).
Well you are right , those are Axis2 transports I mean implement Axis2
transports interfaces so having o.a.axis2 is more meaning full. I mean
those transport can not be used without Axis2.(Even in synapse it uses
Axis2)
> * Users of the transports (other than HTTP) have a better migration
> path from Axis2 1.4.1 to Axis2 1.5. Indeed, the fact that the JMS and
> mail transports are quite different from the old Axis2 versions will
> make it necessary for them to retest (and maybe rework) their
> application. If they can do that independently from the other changes
> in Axis2 1.5, it will probably make things easier for them.
+1
> * The compatibility problem caused by the package renames is only a
> concern for Synapse, not for the whole Axis2 community.
My concern was Axis2 in general.
> * Assuming that people from Synapse participate in the creation of the
> 1.4.2 release and do the work, we could include some fixes that are
> critical to Synapse.
>
> Disadvantage:
> * We can't change the dependency of Synapse trunk to 1.4.2 now,
> because this release doesn't exist yet.
Yes I agree , for that let's try to do 1.4.2 release as soon as we can.
Thank you!
Deepal
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
I'm happy with Paul's proposal. However there is also another
alternative:
1) Keep the org.apache.axis2.transport package name for all transports
(as it is now in trunk).
2) Before creating the first release of the new transports (and
therefore also before the next Synapse release; see point 3), we
create a new Axis2 release 1.4.2, which will basically be 1.4.1 minus
the old transports. Of course the persons volunteering to create that
release may decide to include other critical fixes.
3) The next Synapse release will depend on Axis2 1.4.2 and the first
release of the new transports.
4) In Synapse we implement the compatibility classes I suggested so
that we maintain compatibility at the axis2.xml level (at least for
one release cycle).
Advantages:
* We have a common package name (not a mix of org.apache.axis2 and
org.apache.synapse) that is the same as the original one (before the
Synapse transports were created).
* Users of the transports (other than HTTP) have a better migration
path from Axis2 1.4.1 to Axis2 1.5. Indeed, the fact that the JMS and
mail transports are quite different from the old Axis2 versions will
make it necessary for them to retest (and maybe rework) their
application. If they can do that independently from the other changes
in Axis2 1.5, it will probably make things easier for them.
* The compatibility problem caused by the package renames is only a
concern for Synapse, not for the whole Axis2 community.
* Assuming that people from Synapse participate in the creation of the
1.4.2 release and do the work, we could include some fixes that are
critical to Synapse.
Disadvantage:
* We can't change the dependency of Synapse trunk to 1.4.2 now,
because this release doesn't exist yet.
* Creating release 1.4.2 will probably trigger lots of requests to
include various fixes that people consider important. We can't satisfy
all these requests, in particular because the baseline for that
release will be 1.4.1, not the trunk.
Andreas
On 2 oct. 08, at 19:29, Deepal jayasinghe wrote:
>
>> So how about this for a compromise:
>>
>> 1) We ship all the new transports in separate JARs
>>
> +1 and we can have a single jar containing all the transports as well
> (thats working now)
>> 2) We rename all the transports to a new package name
>>
> I am sorry I am not still convinced to do this change. :-\
>> 3) We do Andreas' suggestion - just for HTTP - so that the old
>> axis2.xml will work
>> 4) Synapse can ship all new transports - everything except the HTTP
>> transport which will be inherited from the current axis2 kernel.
>>
> Yes only for the synapse version that depends on Axis2 1.4.
>
> -Deepal
>> Paul
>>
>> On Thu, Oct 2, 2008 at 6:17 PM, Deepal jayasinghe
>> <de...@gmail.com> wrote:
>>
>>>> I don't see any issue with backward compatibility. This chage is
>>>> something in the axis2.xml, this will not break any code that users
>>>> have with them.
>>>>
>>> Thats exactly my point I should be able to upgrade Axis2 without
>>> changing axis2.xml. If you work with default axis2.xml then you do
>>> not
>>> have any problem , however if you have change your axis2.xml then
>>> you
>>> have to change that. That is the backward compatibility issue I am
>>> talking here :).
>>>
>>>> If it was a API call then I can understand. Also this change would
>>>> not effect generated code (AFAIK).
>>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
I'm happy with Paul's proposal. However there is also another
alternative:
1) Keep the org.apache.axis2.transport package name for all transports
(as it is now in trunk).
2) Before creating the first release of the new transports (and
therefore also before the next Synapse release; see point 3), we
create a new Axis2 release 1.4.2, which will basically be 1.4.1 minus
the old transports. Of course the persons volunteering to create that
release may decide to include other critical fixes.
3) The next Synapse release will depend on Axis2 1.4.2 and the first
release of the new transports.
4) In Synapse we implement the compatibility classes I suggested so
that we maintain compatibility at the axis2.xml level (at least for
one release cycle).
Advantages:
* We have a common package name (not a mix of org.apache.axis2 and
org.apache.synapse) that is the same as the original one (before the
Synapse transports were created).
* Users of the transports (other than HTTP) have a better migration
path from Axis2 1.4.1 to Axis2 1.5. Indeed, the fact that the JMS and
mail transports are quite different from the old Axis2 versions will
make it necessary for them to retest (and maybe rework) their
application. If they can do that independently from the other changes
in Axis2 1.5, it will probably make things easier for them.
* The compatibility problem caused by the package renames is only a
concern for Synapse, not for the whole Axis2 community.
* Assuming that people from Synapse participate in the creation of the
1.4.2 release and do the work, we could include some fixes that are
critical to Synapse.
Disadvantage:
* We can't change the dependency of Synapse trunk to 1.4.2 now,
because this release doesn't exist yet.
* Creating release 1.4.2 will probably trigger lots of requests to
include various fixes that people consider important. We can't satisfy
all these requests, in particular because the baseline for that
release will be 1.4.1, not the trunk.
Andreas
On 2 oct. 08, at 19:29, Deepal jayasinghe wrote:
>
>> So how about this for a compromise:
>>
>> 1) We ship all the new transports in separate JARs
>>
> +1 and we can have a single jar containing all the transports as well
> (thats working now)
>> 2) We rename all the transports to a new package name
>>
> I am sorry I am not still convinced to do this change. :-\
>> 3) We do Andreas' suggestion - just for HTTP - so that the old
>> axis2.xml will work
>> 4) Synapse can ship all new transports - everything except the HTTP
>> transport which will be inherited from the current axis2 kernel.
>>
> Yes only for the synapse version that depends on Axis2 1.4.
>
> -Deepal
>> Paul
>>
>> On Thu, Oct 2, 2008 at 6:17 PM, Deepal jayasinghe
>> <de...@gmail.com> wrote:
>>
>>>> I don't see any issue with backward compatibility. This chage is
>>>> something in the axis2.xml, this will not break any code that users
>>>> have with them.
>>>>
>>> Thats exactly my point I should be able to upgrade Axis2 without
>>> changing axis2.xml. If you work with default axis2.xml then you do
>>> not
>>> have any problem , however if you have change your axis2.xml then
>>> you
>>> have to change that. That is the backward compatibility issue I am
>>> talking here :).
>>>
>>>> If it was a API call then I can understand. Also this change would
>>>> not effect generated code (AFAIK).
>>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
> So how about this for a compromise:
>
> 1) We ship all the new transports in separate JARs
>
+1 and we can have a single jar containing all the transports as well
(thats working now)
> 2) We rename all the transports to a new package name
>
I am sorry I am not still convinced to do this change. :-\
> 3) We do Andreas' suggestion - just for HTTP - so that the old
> axis2.xml will work
> 4) Synapse can ship all new transports - everything except the HTTP
> transport which will be inherited from the current axis2 kernel.
>
Yes only for the synapse version that depends on Axis2 1.4.
-Deepal
> Paul
>
> On Thu, Oct 2, 2008 at 6:17 PM, Deepal jayasinghe <de...@gmail.com> wrote:
>
>>> I don't see any issue with backward compatibility. This chage is
>>> something in the axis2.xml, this will not break any code that users
>>> have with them.
>>>
>> Thats exactly my point I should be able to upgrade Axis2 without
>> changing axis2.xml. If you work with default axis2.xml then you do not
>> have any problem , however if you have change your axis2.xml then you
>> have to change that. That is the backward compatibility issue I am
>> talking here :).
>>
>>> If it was a API call then I can understand. Also this change would
>>> not effect generated code (AFAIK).
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
> So how about this for a compromise:
>
> 1) We ship all the new transports in separate JARs
>
+1 and we can have a single jar containing all the transports as well
(thats working now)
> 2) We rename all the transports to a new package name
>
I am sorry I am not still convinced to do this change. :-\
> 3) We do Andreas' suggestion - just for HTTP - so that the old
> axis2.xml will work
> 4) Synapse can ship all new transports - everything except the HTTP
> transport which will be inherited from the current axis2 kernel.
>
Yes only for the synapse version that depends on Axis2 1.4.
-Deepal
> Paul
>
> On Thu, Oct 2, 2008 at 6:17 PM, Deepal jayasinghe <de...@gmail.com> wrote:
>
>>> I don't see any issue with backward compatibility. This chage is
>>> something in the axis2.xml, this will not break any code that users
>>> have with them.
>>>
>> Thats exactly my point I should be able to upgrade Axis2 without
>> changing axis2.xml. If you work with default axis2.xml then you do not
>> have any problem , however if you have change your axis2.xml then you
>> have to change that. That is the backward compatibility issue I am
>> talking here :).
>>
>>> If it was a API call then I can understand. Also this change would
>>> not effect generated code (AFAIK).
>>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Paul Fremantle <pz...@gmail.com>.
So how about this for a compromise:
1) We ship all the new transports in separate JARs
2) We rename all the transports to a new package name
3) We do Andreas' suggestion - just for HTTP - so that the old
axis2.xml will work
4) Synapse can ship all new transports - everything except the HTTP
transport which will be inherited from the current axis2 kernel.
Paul
On Thu, Oct 2, 2008 at 6:17 PM, Deepal jayasinghe <de...@gmail.com> wrote:
>
>> I don't see any issue with backward compatibility. This chage is
>> something in the axis2.xml, this will not break any code that users
>> have with them.
> Thats exactly my point I should be able to upgrade Axis2 without
> changing axis2.xml. If you work with default axis2.xml then you do not
> have any problem , however if you have change your axis2.xml then you
> have to change that. That is the backward compatibility issue I am
> talking here :).
>> If it was a API call then I can understand. Also this change would
>> not effect generated code (AFAIK).
> I need to double check .
>
> -Deepal
>>
>> Thanks,
>> Keith.
>>
>> On Thu, Oct 2, 2008 at 9:54 PM, Ruwan Linton <ruwan.linton@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>> Hi Deepal,
>>
>> Synapse also has the same backward compatibility issue that you
>> are talking about with the axis2.xml that synapse ships with,
>> therefore shall we keep the transports that synapse community
>> contributed as it is (org.apache.synapse.transports) ;-)
>>
>> Thanks,
>> Ruwan
>>
>>
>> On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe
>> <deepalk@gmail.com <ma...@gmail.com>> wrote:
>>
>>
>> > hi,
>> > the package name that commons transport module use is
>> org.apache.axis2
>> >
>> > I think it should be org.apache.ws.commons
>> Saying no one more time :)
>>
>> I do not think that all the modules in commons should have the
>> package
>> name org.apache.ws.commons , as an example have a look at
>> Axiom and Neethi
>>
>> org.apache.neethi
>> org.apache.axiom
>>
>> So IMO it is ok to have axis2 transport package name as it is :)
>>
>> -Deepal
>> >
>> > WDYT?
>> >
>> > thanks,
>> > Amila.
>> >
>> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
>> > <amilasuriarachchi@gmail.com
>> <ma...@gmail.com>
>> <mailto:amilasuriarachchi@gmail.com
>> <ma...@gmail.com>>> wrote:
>> >
>> >
>> >
>> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>> > <andreas.veithen@skynet.be
>> <ma...@skynet.be>
>> <mailto:andreas.veithen@skynet.be
>> <ma...@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
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> > For additional commands, e-mail:
>> > axis-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>> >
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> > For additional commands, e-mail:
>> axis-dev-help@ws.apache.org <ma...@ws.apache.org>
>> > <mailto:axis-dev-help@ws.apache.org
>> <ma...@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
>> <ma...@synapse.apache.org>
>> For additional commands, e-mail: dev-help@synapse.apache.org
>> <ma...@synapse.apache.org>
>>
>>
>>
>>
>> --
>> Ruwan Linton
>> http://wso2.org - "Oxygenating the Web Services Platform"
>> http://ruwansblog.blogspot.com/
>>
>>
>>
>>
>> --
>> Keith Chapman
>> Senior Software Engineer
>> WSO2 Inc.
>> Oxygenating the Web Service Platform.
>> http://wso2.org/
>>
>> blog: http://www.keith-chapman.org
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Paul Fremantle <pz...@gmail.com>.
So how about this for a compromise:
1) We ship all the new transports in separate JARs
2) We rename all the transports to a new package name
3) We do Andreas' suggestion - just for HTTP - so that the old
axis2.xml will work
4) Synapse can ship all new transports - everything except the HTTP
transport which will be inherited from the current axis2 kernel.
Paul
On Thu, Oct 2, 2008 at 6:17 PM, Deepal jayasinghe <de...@gmail.com> wrote:
>
>> I don't see any issue with backward compatibility. This chage is
>> something in the axis2.xml, this will not break any code that users
>> have with them.
> Thats exactly my point I should be able to upgrade Axis2 without
> changing axis2.xml. If you work with default axis2.xml then you do not
> have any problem , however if you have change your axis2.xml then you
> have to change that. That is the backward compatibility issue I am
> talking here :).
>> If it was a API call then I can understand. Also this change would
>> not effect generated code (AFAIK).
> I need to double check .
>
> -Deepal
>>
>> Thanks,
>> Keith.
>>
>> On Thu, Oct 2, 2008 at 9:54 PM, Ruwan Linton <ruwan.linton@gmail.com
>> <ma...@gmail.com>> wrote:
>>
>> Hi Deepal,
>>
>> Synapse also has the same backward compatibility issue that you
>> are talking about with the axis2.xml that synapse ships with,
>> therefore shall we keep the transports that synapse community
>> contributed as it is (org.apache.synapse.transports) ;-)
>>
>> Thanks,
>> Ruwan
>>
>>
>> On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe
>> <deepalk@gmail.com <ma...@gmail.com>> wrote:
>>
>>
>> > hi,
>> > the package name that commons transport module use is
>> org.apache.axis2
>> >
>> > I think it should be org.apache.ws.commons
>> Saying no one more time :)
>>
>> I do not think that all the modules in commons should have the
>> package
>> name org.apache.ws.commons , as an example have a look at
>> Axiom and Neethi
>>
>> org.apache.neethi
>> org.apache.axiom
>>
>> So IMO it is ok to have axis2 transport package name as it is :)
>>
>> -Deepal
>> >
>> > WDYT?
>> >
>> > thanks,
>> > Amila.
>> >
>> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
>> > <amilasuriarachchi@gmail.com
>> <ma...@gmail.com>
>> <mailto:amilasuriarachchi@gmail.com
>> <ma...@gmail.com>>> wrote:
>> >
>> >
>> >
>> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>> > <andreas.veithen@skynet.be
>> <ma...@skynet.be>
>> <mailto:andreas.veithen@skynet.be
>> <ma...@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
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> > For additional commands, e-mail:
>> > axis-dev-help@ws.apache.org
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-help@ws.apache.org
>> <ma...@ws.apache.org>>
>> >
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail:
>> axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>
>> > <mailto:axis-dev-unsubscribe@ws.apache.org
>> <ma...@ws.apache.org>>
>> > For additional commands, e-mail:
>> axis-dev-help@ws.apache.org <ma...@ws.apache.org>
>> > <mailto:axis-dev-help@ws.apache.org
>> <ma...@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
>> <ma...@synapse.apache.org>
>> For additional commands, e-mail: dev-help@synapse.apache.org
>> <ma...@synapse.apache.org>
>>
>>
>>
>>
>> --
>> Ruwan Linton
>> http://wso2.org - "Oxygenating the Web Services Platform"
>> http://ruwansblog.blogspot.com/
>>
>>
>>
>>
>> --
>> Keith Chapman
>> Senior Software Engineer
>> WSO2 Inc.
>> Oxygenating the Web Service Platform.
>> http://wso2.org/
>>
>> blog: http://www.keith-chapman.org
>
>
> --
> Thank you!
>
>
> http://blogs.deepal.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.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
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
> I don't see any issue with backward compatibility. This chage is
> something in the axis2.xml, this will not break any code that users
> have with them.
Thats exactly my point I should be able to upgrade Axis2 without
changing axis2.xml. If you work with default axis2.xml then you do not
have any problem , however if you have change your axis2.xml then you
have to change that. That is the backward compatibility issue I am
talking here :).
> If it was a API call then I can understand. Also this change would
> not effect generated code (AFAIK).
I need to double check .
-Deepal
>
> Thanks,
> Keith.
>
> On Thu, Oct 2, 2008 at 9:54 PM, Ruwan Linton <ruwan.linton@gmail.com
> <ma...@gmail.com>> wrote:
>
> Hi Deepal,
>
> Synapse also has the same backward compatibility issue that you
> are talking about with the axis2.xml that synapse ships with,
> therefore shall we keep the transports that synapse community
> contributed as it is (org.apache.synapse.transports) ;-)
>
> Thanks,
> Ruwan
>
>
> On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe
> <deepalk@gmail.com <ma...@gmail.com>> wrote:
>
>
> > hi,
> > the package name that commons transport module use is
> org.apache.axis2
> >
> > I think it should be org.apache.ws.commons
> Saying no one more time :)
>
> I do not think that all the modules in commons should have the
> package
> name org.apache.ws.commons , as an example have a look at
> Axiom and Neethi
>
> org.apache.neethi
> org.apache.axiom
>
> So IMO it is ok to have axis2 transport package name as it is :)
>
> -Deepal
> >
> > WDYT?
> >
> > thanks,
> > Amila.
> >
> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
> > <amilasuriarachchi@gmail.com
> <ma...@gmail.com>
> <mailto:amilasuriarachchi@gmail.com
> <ma...@gmail.com>>> wrote:
> >
> >
> >
> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> > <andreas.veithen@skynet.be
> <ma...@skynet.be>
> <mailto:andreas.veithen@skynet.be
> <ma...@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
> <ma...@ws.apache.org>
> > <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> > For additional commands, e-mail:
> > axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> > <mailto:axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> > <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> > For additional commands, e-mail:
> axis-dev-help@ws.apache.org <ma...@ws.apache.org>
> > <mailto:axis-dev-help@ws.apache.org
> <ma...@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
> <ma...@synapse.apache.org>
> For additional commands, e-mail: dev-help@synapse.apache.org
> <ma...@synapse.apache.org>
>
>
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
--
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
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
> I don't see any issue with backward compatibility. This chage is
> something in the axis2.xml, this will not break any code that users
> have with them.
Thats exactly my point I should be able to upgrade Axis2 without
changing axis2.xml. If you work with default axis2.xml then you do not
have any problem , however if you have change your axis2.xml then you
have to change that. That is the backward compatibility issue I am
talking here :).
> If it was a API call then I can understand. Also this change would
> not effect generated code (AFAIK).
I need to double check .
-Deepal
>
> Thanks,
> Keith.
>
> On Thu, Oct 2, 2008 at 9:54 PM, Ruwan Linton <ruwan.linton@gmail.com
> <ma...@gmail.com>> wrote:
>
> Hi Deepal,
>
> Synapse also has the same backward compatibility issue that you
> are talking about with the axis2.xml that synapse ships with,
> therefore shall we keep the transports that synapse community
> contributed as it is (org.apache.synapse.transports) ;-)
>
> Thanks,
> Ruwan
>
>
> On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe
> <deepalk@gmail.com <ma...@gmail.com>> wrote:
>
>
> > hi,
> > the package name that commons transport module use is
> org.apache.axis2
> >
> > I think it should be org.apache.ws.commons
> Saying no one more time :)
>
> I do not think that all the modules in commons should have the
> package
> name org.apache.ws.commons , as an example have a look at
> Axiom and Neethi
>
> org.apache.neethi
> org.apache.axiom
>
> So IMO it is ok to have axis2 transport package name as it is :)
>
> -Deepal
> >
> > WDYT?
> >
> > thanks,
> > Amila.
> >
> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
> > <amilasuriarachchi@gmail.com
> <ma...@gmail.com>
> <mailto:amilasuriarachchi@gmail.com
> <ma...@gmail.com>>> wrote:
> >
> >
> >
> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> > <andreas.veithen@skynet.be
> <ma...@skynet.be>
> <mailto:andreas.veithen@skynet.be
> <ma...@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
> <ma...@ws.apache.org>
> > <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> > For additional commands, e-mail:
> > axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> > <mailto:axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> > <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> > For additional commands, e-mail:
> axis-dev-help@ws.apache.org <ma...@ws.apache.org>
> > <mailto:axis-dev-help@ws.apache.org
> <ma...@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
> <ma...@synapse.apache.org>
> For additional commands, e-mail: dev-help@synapse.apache.org
> <ma...@synapse.apache.org>
>
>
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
>
>
>
>
> --
> Keith Chapman
> Senior Software Engineer
> WSO2 Inc.
> Oxygenating the Web Service Platform.
> http://wso2.org/
>
> blog: http://www.keith-chapman.org
--
Thank you!
http://blogs.deepal.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by keith chapman <ke...@gmail.com>.
I don't see any issue with backward compatibility. This chage is something
in the axis2.xml, this will not break any code that users have with them. If
it was a API call then I can understand. Also this change would not effect
generated code (AFAIK).
Thanks,
Keith.
On Thu, Oct 2, 2008 at 9:54 PM, Ruwan Linton <ru...@gmail.com> wrote:
> Hi Deepal,
>
> Synapse also has the same backward compatibility issue that you are talking
> about with the axis2.xml that synapse ships with, therefore shall we keep
> the transports that synapse community contributed as it is
> (org.apache.synapse.transports) ;-)
>
> Thanks,
> Ruwan
>
>
> On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe <de...@gmail.com>wrote:
>
>>
>> > hi,
>> > the package name that commons transport module use is org.apache.axis2
>> >
>> > I think it should be org.apache.ws.commons
>> Saying no one more time :)
>>
>> I do not think that all the modules in commons should have the package
>> name org.apache.ws.commons , as an example have a look at Axiom and Neethi
>>
>> org.apache.neethi
>> org.apache.axiom
>>
>> So IMO it is ok to have axis2 transport package name as it is :)
>>
>> -Deepal
>> >
>> > WDYT?
>> >
>> > thanks,
>> > Amila.
>> >
>> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
>> > <amilasuriarachchi@gmail.com <ma...@gmail.com>>
>> wrote:
>> >
>> >
>> >
>> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>> > <andreas.veithen@skynet.be <ma...@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
>> > <ma...@ws.apache.org>
>> > For additional commands, e-mail:
>> > axis-dev-help@ws.apache.org
>> > <ma...@ws.apache.org>
>> >
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> > <ma...@ws.apache.org>
>> > For additional commands, e-mail: axis-dev-help@ws.apache.org
>> > <ma...@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
>>
>>
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: [Axis2] Moving all the transports into a common modules
Posted by keith chapman <ke...@gmail.com>.
On Thu, Oct 2, 2008 at 9:54 PM, Ruwan Linton <ru...@gmail.com> wrote:
> Hi Deepal,
>
> Synapse also has the same backward compatibility issue that you are talking
> about with the axis2.xml that synapse ships with, therefore shall we keep
> the transports that synapse community contributed as it is
> (org.apache.synapse.transports) ;-)
>
Another good reason to have a common package name. ;).
Thanks,
Keith.
>
>
> Thanks,
> Ruwan
>
>
> On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe <de...@gmail.com>wrote:
>
>>
>> > hi,
>> > the package name that commons transport module use is org.apache.axis2
>> >
>> > I think it should be org.apache.ws.commons
>> Saying no one more time :)
>>
>> I do not think that all the modules in commons should have the package
>> name org.apache.ws.commons , as an example have a look at Axiom and Neethi
>>
>> org.apache.neethi
>> org.apache.axiom
>>
>> So IMO it is ok to have axis2 transport package name as it is :)
>>
>> -Deepal
>> >
>> > WDYT?
>> >
>> > thanks,
>> > Amila.
>> >
>> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
>> > <amilasuriarachchi@gmail.com <ma...@gmail.com>>
>> wrote:
>> >
>> >
>> >
>> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>> > <andreas.veithen@skynet.be <ma...@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
>> > <ma...@ws.apache.org>
>> > For additional commands, e-mail:
>> > axis-dev-help@ws.apache.org
>> > <ma...@ws.apache.org>
>> >
>> >
>> >
>> >
>> ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> > <ma...@ws.apache.org>
>> > For additional commands, e-mail: axis-dev-help@ws.apache.org
>> > <ma...@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
>>
>>
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
>
--
Keith Chapman
Senior Software Engineer
WSO2 Inc.
Oxygenating the Web Service Platform.
http://wso2.org/
blog: http://www.keith-chapman.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
We can easily guarantee backward compatibility (for axis2.xml) by having
a set of classes with the old package names and extending the
corresponding classes in the new version. Since this is only needed for
transport listeners/senders and message formatters/builders, it would
not require too much effort.
Andreas
Ruwan Linton wrote:
> Hi Deepal,
>
> Synapse also has the same backward compatibility issue that you are
> talking about with the axis2.xml that synapse ships with, therefore
> shall we keep the transports that synapse community contributed as it
> is (org.apache.synapse.transports) ;-)
>
> Thanks,
> Ruwan
>
> On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe <deepalk@gmail.com
> <ma...@gmail.com>> wrote:
>
>
> > hi,
> > the package name that commons transport module use is
> org.apache.axis2
> >
> > I think it should be org.apache.ws.commons
> Saying no one more time :)
>
> I do not think that all the modules in commons should have the package
> name org.apache.ws.commons , as an example have a look at Axiom
> and Neethi
>
> org.apache.neethi
> org.apache.axiom
>
> So IMO it is ok to have axis2 transport package name as it is :)
>
> -Deepal
> >
> > WDYT?
> >
> > thanks,
> > Amila.
> >
> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
> > <amilasuriarachchi@gmail.com
> <ma...@gmail.com>
> <mailto:amilasuriarachchi@gmail.com
> <ma...@gmail.com>>> wrote:
> >
> >
> >
> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> > <andreas.veithen@skynet.be
> <ma...@skynet.be>
> <mailto:andreas.veithen@skynet.be
> <ma...@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
> <ma...@ws.apache.org>
> > <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> > For additional commands, e-mail:
> > axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
> > <mailto:axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>>
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> > <mailto:axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>>
> > For additional commands, e-mail:
> axis-dev-help@ws.apache.org <ma...@ws.apache.org>
> > <mailto:axis-dev-help@ws.apache.org
> <ma...@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
> <ma...@synapse.apache.org>
> For additional commands, e-mail: dev-help@synapse.apache.org
> <ma...@synapse.apache.org>
>
>
>
>
> --
> Ruwan Linton
> http://wso2.org - "Oxygenating the Web Services Platform"
> http://ruwansblog.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Ruwan Linton <ru...@gmail.com>.
Hi Deepal,
Synapse also has the same backward compatibility issue that you are talking
about with the axis2.xml that synapse ships with, therefore shall we keep
the transports that synapse community contributed as it is
(org.apache.synapse.transports) ;-)
Thanks,
Ruwan
On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe <de...@gmail.com> wrote:
>
> > hi,
> > the package name that commons transport module use is org.apache.axis2
> >
> > I think it should be org.apache.ws.commons
> Saying no one more time :)
>
> I do not think that all the modules in commons should have the package
> name org.apache.ws.commons , as an example have a look at Axiom and Neethi
>
> org.apache.neethi
> org.apache.axiom
>
> So IMO it is ok to have axis2 transport package name as it is :)
>
> -Deepal
> >
> > WDYT?
> >
> > thanks,
> > Amila.
> >
> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
> > <amilasuriarachchi@gmail.com <ma...@gmail.com>>
> wrote:
> >
> >
> >
> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> > <andreas.veithen@skynet.be <ma...@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
> > <ma...@ws.apache.org>
> > For additional commands, e-mail:
> > axis-dev-help@ws.apache.org
> > <ma...@ws.apache.org>
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > <ma...@ws.apache.org>
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > <ma...@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
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by Ruwan Linton <ru...@gmail.com>.
Hi Deepal,
Synapse also has the same backward compatibility issue that you are talking
about with the axis2.xml that synapse ships with, therefore shall we keep
the transports that synapse community contributed as it is
(org.apache.synapse.transports) ;-)
Thanks,
Ruwan
On Thu, Oct 2, 2008 at 9:01 PM, Deepal jayasinghe <de...@gmail.com> wrote:
>
> > hi,
> > the package name that commons transport module use is org.apache.axis2
> >
> > I think it should be org.apache.ws.commons
> Saying no one more time :)
>
> I do not think that all the modules in commons should have the package
> name org.apache.ws.commons , as an example have a look at Axiom and Neethi
>
> org.apache.neethi
> org.apache.axiom
>
> So IMO it is ok to have axis2 transport package name as it is :)
>
> -Deepal
> >
> > WDYT?
> >
> > thanks,
> > Amila.
> >
> > On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
> > <amilasuriarachchi@gmail.com <ma...@gmail.com>>
> wrote:
> >
> >
> >
> > On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> > <andreas.veithen@skynet.be <ma...@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
> > <ma...@ws.apache.org>
> > For additional commands, e-mail:
> > axis-dev-help@ws.apache.org
> > <ma...@ws.apache.org>
> >
> >
> >
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> > <ma...@ws.apache.org>
> > For additional commands, e-mail: axis-dev-help@ws.apache.org
> > <ma...@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
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
RE: [Axis2] Moving all the transports into a common modules
Posted by Tom Jordahl <tj...@adobe.com>.
I am with Deepal on this, why change if there is no eral gain and possible user pain.
Tom Jordahl
-----Original Message-----
From: Deepal jayasinghe [mailto:deepalk@gmail.com]
Sent: Thursday, October 02, 2008 11:32 AM
To: dev@synapse.apache.org
Cc: axis-dev@ws.apache.org
Subject: Re: [Axis2] Moving all the transports into a common modules
> hi,
> the package name that commons transport module use is org.apache.axis2
>
> I think it should be org.apache.ws.commons
Saying no one more time :)
I do not think that all the modules in commons should have the package
name org.apache.ws.commons , as an example have a look at Axiom and Neethi
org.apache.neethi
org.apache.axiom
So IMO it is ok to have axis2 transport package name as it is :)
-Deepal
>
> WDYT?
>
> thanks,
> Amila.
>
> On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
> <amilasuriarachchi@gmail.com <ma...@gmail.com>> wrote:
>
>
>
> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> <andreas.veithen@skynet.be <ma...@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
> <ma...@ws.apache.org>
> For additional commands, e-mail:
> axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
RE: [Axis2] Moving all the transports into a common modules
Posted by Tom Jordahl <tj...@adobe.com>.
I am with Deepal on this, why change if there is no eral gain and possible user pain.
Tom Jordahl
-----Original Message-----
From: Deepal jayasinghe [mailto:deepalk@gmail.com]
Sent: Thursday, October 02, 2008 11:32 AM
To: dev@synapse.apache.org
Cc: axis-dev@ws.apache.org
Subject: Re: [Axis2] Moving all the transports into a common modules
> hi,
> the package name that commons transport module use is org.apache.axis2
>
> I think it should be org.apache.ws.commons
Saying no one more time :)
I do not think that all the modules in commons should have the package
name org.apache.ws.commons , as an example have a look at Axiom and Neethi
org.apache.neethi
org.apache.axiom
So IMO it is ok to have axis2 transport package name as it is :)
-Deepal
>
> WDYT?
>
> thanks,
> Amila.
>
> On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
> <amilasuriarachchi@gmail.com <ma...@gmail.com>> wrote:
>
>
>
> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> <andreas.veithen@skynet.be <ma...@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
> <ma...@ws.apache.org>
> For additional commands, e-mail:
> axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
> hi,
> the package name that commons transport module use is org.apache.axis2
>
> I think it should be org.apache.ws.commons
Saying no one more time :)
I do not think that all the modules in commons should have the package
name org.apache.ws.commons , as an example have a look at Axiom and Neethi
org.apache.neethi
org.apache.axiom
So IMO it is ok to have axis2 transport package name as it is :)
-Deepal
>
> WDYT?
>
> thanks,
> Amila.
>
> On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
> <amilasuriarachchi@gmail.com <ma...@gmail.com>> wrote:
>
>
>
> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> <andreas.veithen@skynet.be <ma...@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
> <ma...@ws.apache.org>
> For additional commands, e-mail:
> axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@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
Re: [Axis2] Moving all the transports into a common modules
Posted by Deepal jayasinghe <de...@gmail.com>.
> hi,
> the package name that commons transport module use is org.apache.axis2
>
> I think it should be org.apache.ws.commons
Saying no one more time :)
I do not think that all the modules in commons should have the package
name org.apache.ws.commons , as an example have a look at Axiom and Neethi
org.apache.neethi
org.apache.axiom
So IMO it is ok to have axis2 transport package name as it is :)
-Deepal
>
> WDYT?
>
> thanks,
> Amila.
>
> On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi
> <amilasuriarachchi@gmail.com <ma...@gmail.com>> wrote:
>
>
>
> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> <andreas.veithen@skynet.be <ma...@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
> <ma...@ws.apache.org>
> For additional commands, e-mail:
> axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@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: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Amila Suriarachchi <am...@gmail.com>.
hi,
the package name that commons transport module use is org.apache.axis2
I think it should be org.apache.ws.commons
WDYT?
thanks,
Amila.
On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen <
> 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
>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by Ruwan Linton <ru...@gmail.com>.
+1 for moving these transports.
Thanks,
Ruwan
On Mon, Sep 22, 2008 at 1:37 PM, Asankha C. Perera <as...@wso2.com> wrote:
> Hi all
>
> I will be moving the Mail, JMS and the Base Transport abstraction into the
> WS Commons project now.
>
> Then on WS-Commons dev list (CC:ing axis2-dev), I will be calling for a
> vote for commit rights to Andreas, so that he can help maintain the codebase
>
> We will consider moving other transports on a case-by-case basis, if there
> will be an advantage for them for plain Axis2 as well.
>
> asankha
>
> Andreas Veithen wrote:
>
>> Amila,
>>
>> Please don't move anything for the moment. We need to make sure that this
>> is well coordinated before doing anything. I will come back on this later.
>>
>> Andreas
>>
>> Amila Suriarachchi wrote:
>>
>>>
>>>
>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen <
>>> andreas.veithen@skynet.be <ma...@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.
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by "Asankha C. Perera" <as...@wso2.com>.
Andreas
Andreas Veithen wrote:
> Can you please wait with this another 8 hours?
>
> Andreas
I've already moved the code.. and now I'm finishing up the changes
asankha
>
> Quoting "Asankha C. Perera" <as...@wso2.com>:
>
>> Hi all
>>
>> I will be moving the Mail, JMS and the Base Transport abstraction into
>> the WS Commons project now.
>>
>> Then on WS-Commons dev list (CC:ing axis2-dev), I will be calling for a
>> vote for commit rights to Andreas, so that he can help maintain the
>> codebase
>>
>> We will consider moving other transports on a case-by-case basis, if
>> there will be an advantage for them for plain Axis2 as well.
>>
>> asankha
>>
>> Andreas Veithen wrote:
>>> Amila,
>>>
>>> Please don't move anything for the moment. We need to make sure
>>> that this is well coordinated before doing anything. I will come
>>> back on this later.
>>>
>>> Andreas
>>>
>>> Amila Suriarachchi wrote:
>>>>
>>>>
>>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>>> <andreas.veithen@skynet.be <ma...@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.
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
>> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
Can you please wait with this another 8 hours?
Andreas
Quoting "Asankha C. Perera" <as...@wso2.com>:
> Hi all
>
> I will be moving the Mail, JMS and the Base Transport abstraction into
> the WS Commons project now.
>
> Then on WS-Commons dev list (CC:ing axis2-dev), I will be calling for a
> vote for commit rights to Andreas, so that he can help maintain the
> codebase
>
> We will consider moving other transports on a case-by-case basis, if
> there will be an advantage for them for plain Axis2 as well.
>
> asankha
>
> Andreas Veithen wrote:
>> Amila,
>>
>> Please don't move anything for the moment. We need to make sure
>> that this is well coordinated before doing anything. I will come
>> back on this later.
>>
>> Andreas
>>
>> Amila Suriarachchi wrote:
>>>
>>>
>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>> <andreas.veithen@skynet.be <ma...@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.
>>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Ruwan Linton <ru...@gmail.com>.
+1 for moving these transports,
Thanks,
Ruwan
On Mon, Sep 22, 2008 at 1:37 PM, Asankha C. Perera <as...@wso2.com> wrote:
> Hi all
>
> I will be moving the Mail, JMS and the Base Transport abstraction into the
> WS Commons project now.
>
> Then on WS-Commons dev list (CC:ing axis2-dev), I will be calling for a
> vote for commit rights to Andreas, so that he can help maintain the codebase
>
> We will consider moving other transports on a case-by-case basis, if there
> will be an advantage for them for plain Axis2 as well.
>
> asankha
>
> Andreas Veithen wrote:
>
>> Amila,
>>
>> Please don't move anything for the moment. We need to make sure that this
>> is well coordinated before doing anything. I will come back on this later.
>>
>> Andreas
>>
>> Amila Suriarachchi wrote:
>>
>>>
>>>
>>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen <
>>> andreas.veithen@skynet.be <ma...@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.
>>>
>>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
> For additional commands, e-mail: dev-help@synapse.apache.org
>
>
--
Ruwan Linton
http://wso2.org - "Oxygenating the Web Services Platform"
http://ruwansblog.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi all
I will be moving the Mail, JMS and the Base Transport abstraction into
the WS Commons project now.
Then on WS-Commons dev list (CC:ing axis2-dev), I will be calling for a
vote for commit rights to Andreas, so that he can help maintain the codebase
We will consider moving other transports on a case-by-case basis, if
there will be an advantage for them for plain Axis2 as well.
asankha
Andreas Veithen wrote:
> Amila,
>
> Please don't move anything for the moment. We need to make sure that
> this is well coordinated before doing anything. I will come back on
> this later.
>
> Andreas
>
> Amila Suriarachchi wrote:
>>
>>
>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>> <andreas.veithen@skynet.be <ma...@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.
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi all
I will be moving the Mail, JMS and the Base Transport abstraction into
the WS Commons project now.
Then on WS-Commons dev list (CC:ing axis2-dev), I will be calling for a
vote for commit rights to Andreas, so that he can help maintain the codebase
We will consider moving other transports on a case-by-case basis, if
there will be an advantage for them for plain Axis2 as well.
asankha
Andreas Veithen wrote:
> Amila,
>
> Please don't move anything for the moment. We need to make sure that
> this is well coordinated before doing anything. I will come back on
> this later.
>
> Andreas
>
> Amila Suriarachchi wrote:
>>
>>
>> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>> <andreas.veithen@skynet.be <ma...@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.
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
Amila,
Please don't move anything for the moment. We need to make sure that
this is well coordinated before doing anything. I will come back on this
later.
Andreas
Amila Suriarachchi wrote:
>
>
> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> <andreas.veithen@skynet.be <ma...@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
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
Amila,
Please don't move anything for the moment. We need to make sure that
this is well coordinated before doing anything. I will come back on this
later.
Andreas
Amila Suriarachchi wrote:
>
>
> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
> <andreas.veithen@skynet.be <ma...@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
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-dev-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Amila Suriarachchi <am...@gmail.com>.
hi,
the package name that commons transport module use is org.apache.axis2
I think it should be org.apache.ws.commons
WDYT?
thanks,
Amila.
On Mon, Sep 22, 2008 at 12:03 PM, Amila Suriarachchi <
amilasuriarachchi@gmail.com> wrote:
>
>
> On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen <
> 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
>>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
>
> --
> Amila Suriarachchi
> WSO2 Inc.
> blog: http://amilachinthaka.blogspot.com/
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by Amila Suriarachchi <am...@gmail.com>.
On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
<an...@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
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by Amila Suriarachchi <am...@gmail.com>.
On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
<an...@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.
Shall we first move JMS and SMTP. if you can move them from Synapse to ws
commons transport then I can test them 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
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by Amila Suriarachchi <am...@gmail.com>.
On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
<an...@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
>> For additional commands, e-mail: axis-dev-help@ws.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
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.
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
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org
Re: [Axis2] Moving all the transports into a common modules
Posted by Andreas Veithen <an...@skynet.be>.
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.
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
> For additional commands, e-mail: axis-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org