You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@synapse.apache.org by Paul Fremantle <pz...@gmail.com> on 2008/10/02 15:41:13 UTC
Re: [Axis2] Moving all the transports into a common modules
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>.
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