synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Deepal jayasinghe <>
Subject Re: [Axis2] Moving all the transports into a common modules
Date Thu, 02 Oct 2008 17:29:49 GMT

> 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.

> Paul
> On Thu, Oct 2, 2008 at 6:17 PM, Deepal jayasinghe <> 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:
For additional commands, e-mail:

View raw message