I also agree - let's do for APIs first and then look at proxies. Paul
On Sat, Feb 25, 2012 at 12:30 PM, Sanjiva Weerawarana <[email protected] > wrote: > On Fri, Feb 24, 2012 at 10:40 PM, Udayanga Wickramasinghe < > [email protected]> wrote: > >> >> >> On Fri, Feb 24, 2012 at 8:54 PM, Paul Fremantle <[email protected]> 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. > > Anyway +1 for getting it sorted for APIs first. > > Sanjiva. > -- > Sanjiva Weerawarana, Ph.D. > Founder, Director & Chief Scientist; Lanka Software Foundation; > http://www.opensource.lk/ > Founder, Chairman & CEO; WSO2; http://wso2.com/ > Founder & Director; Thinkcube Systems; http://www.thinkcube.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/ > > -- 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
