Return-Path: X-Original-To: apmail-synapse-dev-archive@www.apache.org Delivered-To: apmail-synapse-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 2865C9A54 for ; Fri, 24 Feb 2012 17:11:26 +0000 (UTC) Received: (qmail 99160 invoked by uid 500); 24 Feb 2012 17:11:26 -0000 Delivered-To: apmail-synapse-dev-archive@synapse.apache.org Received: (qmail 99118 invoked by uid 500); 24 Feb 2012 17:11:25 -0000 Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@synapse.apache.org Delivered-To: mailing list dev@synapse.apache.org Received: (qmail 99111 invoked by uid 99); 24 Feb 2012 17:11:25 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Feb 2012 17:11:25 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of udayanga@wso2.com designates 209.85.215.42 as permitted sender) Received: from [209.85.215.42] (HELO mail-lpp01m010-f42.google.com) (209.85.215.42) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 24 Feb 2012 17:11:19 +0000 Received: by lagk11 with SMTP id k11so3228496lag.15 for ; Fri, 24 Feb 2012 09:10:58 -0800 (PST) Received-SPF: pass (google.com: domain of udayanga@wso2.com designates 10.152.147.38 as permitted sender) client-ip=10.152.147.38; Authentication-Results: mr.google.com; spf=pass (google.com: domain of udayanga@wso2.com designates 10.152.147.38 as permitted sender) smtp.mail=udayanga@wso2.com Received: from mr.google.com ([10.152.147.38]) by 10.152.147.38 with SMTP id th6mr2479571lab.47.1330103458311 (num_hops = 1); Fri, 24 Feb 2012 09:10:58 -0800 (PST) Received: by 10.152.147.38 with SMTP id th6mr2028391lab.47.1330103458074; Fri, 24 Feb 2012 09:10:58 -0800 (PST) MIME-Version: 1.0 Received: by 10.112.82.99 with HTTP; Fri, 24 Feb 2012 09:10:37 -0800 (PST) In-Reply-To: References: From: Udayanga Wickramasinghe Date: Fri, 24 Feb 2012 22:40:37 +0530 Message-ID: Subject: Re: API versioning for Synapse Resources... To: dev@synapse.apache.org Content-Type: multipart/alternative; boundary=e89a8f22bdc5220fd904b9b8d816 X-Gm-Message-State: ALoCoQkIlOk63+MjSufVxBPYFIEeJmi3LbHOhDOwHD1CM/3IjmMKia8edBMdZ1eCbboWVAXzrIYI X-Virus-Checked: Checked by ClamAV on apache.org --e89a8f22bdc5220fd904b9b8d816 Content-Type: text/plain; charset=ISO-8859-1 On Fri, Feb 24, 2012 at 8:54 PM, Paul Fremantle 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.. Paul > > > On Thu, Feb 23, 2012 at 8:38 AM, Udayanga Wickramasinghe < > udayanga@wso2.com> wrote: > >> Hi, >> >> On Wed, Feb 22, 2012 at 6:47 PM, Udayanga Wickramasinghe < >> udayanga@wso2.com> wrote: >> >>> Hi, >>> I think it would be great to have versioning capability for ESB API >>> resources.. >>> For example following could be the draft schemas of API's that can be >>> deployed as resources of the same version... >>> >>> >>> >> inSequence="..." outSequence="..."/> >>> >> inSequence="...." outSequence="..." /> >>> ................... >>> .............. >>> ..... >>> >>> >>> We need to (optionally) include a *version-param* attribute as well >> (ie:- which can be used to extract the actual version)..Sorry i missed it >> earlier...Modified schema is the following.. >> >> >> >> ........... >> ...... >> >> >> Regards, >> udayanga >> >> -- >> *Udayanga Wickramasinghe* >> Software Engineer; WSO2 Inc.; http://wso2.com, >> *email: **udayanga@wso2.com* * cell: +94 (77) >> 983-4365 >> blog: **http://udayangawiki.blogspot.com* >> * >> twitter: **http://twitter.com/udayanga_wick* >> * >> * >> > > > > -- > 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 > -- *Udayanga Wickramasinghe* Software Engineer; WSO2 Inc.; http://wso2.com, *email: **udayanga@wso2.com* * cell: +94 (77) 983-4365 blog: **http://udayangawiki.blogspot.com* * twitter: **http://twitter.com/udayanga_wick* * * --e89a8f22bdc5220fd904b9b8d816 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable

On Fri, Feb 24, 2012 at 8:54 PM, Paul Fr= emantle <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 version= ing strategy for proxies we might need to do changes in axis2 as well..
Paul


On Thu, Feb 23, 2012 at 8= :38 AM, Udayanga Wickramasinghe <udayanga@wso2.com> wrote:
Hi,

On Wed, Feb 22, 2012 at 6:47 PM, Udayanga Wickramasinghe = <udayanga@wso2.com> wrote:
Hi,
I think it would be great to have versioning capability for ESB API = resources..
For example following could be the draft schemas of API'= s that can be deployed as resources of the same version...

=A0=A0= =A0 <api name=3D"AccountManagementAPI" version=3D&qu= ot;1.0.0" version-type=3D"url | header | query-param | ..&= quot; context=3D"/am">=A0=A0=A0 =A0=A0=A0
=A0=A0=A0 =A0=A0=A0 <resource uri-template=3D"/account/{accountId}&= quot; methods=3D"GET" inSequence=3D"..." outSequence=3D= "..."/>=A0=A0=A0 =A0=A0=A0 =A0=A0=A0 =A0=A0=A0 =A0=A0=A0
=A0=A0=A0 =A0=A0=A0 <resource uri-template=3D"/account/{accountId}&= quot; methods=3D"PUT" inSequence=3D"...." outSequence= =3D"..." />
=A0=A0=A0=A0=A0=A0=A0 ...................
= =A0=A0=A0=A0=A0=A0=A0 ..............
=A0=A0=A0=A0=A0=A0=A0 .....
=A0=A0=A0 </api>=A0=A0=A0

We need to = (optionally) include a version-param attribute as well (ie:- which c= an be used to extract the actual version)..Sorry i missed it earlier...Modi= fied schema is the following..

<api name=3D"AccountManagementAPI" version=3D&q= uot;1.0.0" version-type=3D"url | header | query-param | .." version-param=3D"regex | str= ing"=A0 context=3D"/am">=A0=A0=A0 =A0=A0=A0 ...........
......
</api>

Regards,
udayanga

=
--
Udayanga Wickramasinghe
Software Engineer; WSO2 Inc.; http://wso2.com,
email: udayanga@wso2.com= =20 cell: +94 (77) 983-4365
blog: http://udayangawiki.blogspot.com=
twitter: http://twitter.com/udayanga_wi= ck




<= /div>--
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



--
Udayanga Wickramasin= ghe
Software Engineer; WSO2 Inc.; http://wso2.com,
email: udayanga@wso2.com= =20 cell: +94 (77) 983-4365
blog: http://udayangawiki.blogspot.com=
twitter: http://twitter.com/udayanga_wi= ck

--e89a8f22bdc5220fd904b9b8d816--