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 <[EMAIL PROTECTED]> 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 <[EMAIL PROTECTED]
>> <mailto:[EMAIL PROTECTED]>> 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
>>     <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>> 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
>>         > <[EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>
>>         <mailto:[EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>>> wrote:
>>         >
>>         >
>>         >
>>         >     On Sun, Sep 21, 2008 at 2:59 PM, Andreas Veithen
>>         >     <[EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>
>>         <mailto:[EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>>> 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:
>>         [EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>
>>         >             <mailto:[EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>>
>>         >             For additional commands, e-mail:
>>         >             [EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>
>>         >             <mailto:[EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>>
>>         >
>>         >
>>         >
>>         >
>>         ---------------------------------------------------------------------
>>         >         To unsubscribe, e-mail:
>>         [EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>
>>         >         <mailto:[EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>>
>>         >         For additional commands, e-mail:
>>         [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>
>>         >         <mailto:[EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>>
>>         >
>>         >
>>         >
>>         >
>>         >     --
>>         >     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: [EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>
>>         For additional commands, e-mail: [EMAIL PROTECTED]
>>         <mailto:[EMAIL PROTECTED]>
>>
>>
>>
>>
>>     --
>>     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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>



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

blog: http://pzf.fremantle.org
[EMAIL PROTECTED]

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

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to