synapse-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Udayanga Wickramasinghe <udaya...@wso2.com>
Subject Re: API versioning for Synapse Resources...
Date Sun, 26 Feb 2012 05:12:44 GMT
On Sat, Feb 25, 2012 at 6:00 PM, Sanjiva Weerawarana
<sanjiva@opensource.lk>wrote:

> On Fri, Feb 24, 2012 at 10:40 PM, Udayanga Wickramasinghe <
> udayanga@wso2.com> wrote:
>
>>
>>
>> On Fri, Feb 24, 2012 at 8:54 PM, Paul Fremantle <pzfreo@gmail.com> wrote:
>>
>>> Should we consider the same for proxies too?
>>>
>>> +1 ..i think it would be very useful for both API's and proxies..but
>> let's start with for API resources...
>> i guess to implement a versioning strategy for proxies we might need to
>> do changes in axis2 as well..
>>
>
> +1 but I don't think it requires a change to Axis2 .. can it not be done
> as a handler that does the version selection as part of dispatch? Basically
> we write a "Version Dispatcher" and have it append the version # to the
> AxisService name.
>
> yes that is true.. either we have to incorporate a logical version into
the name itself ( thus a version embedded proxy service name) OR find
explicit version support in axis2..

Regards,
udayanga--

*Udayanga Wickramasinghe*
Software Engineer; WSO2 Inc.; http://wso2.com,
*email: **udayanga@wso2.com* <udayangaw@wso2.com>* cell: +94 (77) 983-4365
blog: **http://udayangawiki.blogspot.com*<http://udayangawiki.blogspot.com/>
*
twitter: **http://twitter.com/udayanga_wick*<http://twitter.com/udayanga_wick>
*
*

Mime
View raw message