Return-Path: 
 <dev-return-5931-apmail-synapse-dev-archive=synapse.apache.org@synapse.apache.org>
Delivered-To: apmail-synapse-dev-archive@www.apache.org
Received: (qmail 11692 invoked from network); 6 Mar 2008 06:52:46 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 6 Mar 2008 06:52:46 -0000
Received: (qmail 82924 invoked by uid 500); 6 Mar 2008 06:52:42 -0000
Delivered-To: apmail-synapse-dev-archive@synapse.apache.org
Received: (qmail 82882 invoked by uid 500); 6 Mar 2008 06:52:41 -0000
Mailing-List: contact dev-help@synapse.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:dev-help@synapse.apache.org>
List-Unsubscribe: <mailto:dev-unsubscribe@synapse.apache.org>
List-Post: <mailto:dev@synapse.apache.org>
List-Id: <dev.synapse.apache.org>
Reply-To: dev@synapse.apache.org
Delivered-To: mailing list dev@synapse.apache.org
Received: (qmail 82873 invoked by uid 99); 6 Mar 2008 06:52:41 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Mar 2008 22:52:41 -0800
X-ASF-Spam-Status: No, hits=0.0 required=10.0
	tests=SPF_PASS,WHOIS_NETSOLPR
X-Spam-Check-By: apache.org
Received-SPF: pass (athena.apache.org: domain of pzfreo@gmail.com designates
 209.85.198.184 as permitted sender)
Received: from [209.85.198.184] (HELO rv-out-0910.google.com) (209.85.198.184)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 06 Mar 2008 06:52:04 +0000
Received: by rv-out-0910.google.com with SMTP id k15so1011618rvb.51
        for <dev@synapse.apache.org>; Wed, 05 Mar 2008 22:52:13 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        bh=orZvgaVaLsWhFFWhh8iJALf3uJKv00zJ8xGtzV5YnTg=;
        b=mGAAcA/T969OeWa3KcrJlP0XYLv9GoRsqrtz1YEdB3q3J86nf/PbhVujHUKURlg5N5nxpoCNJcfS304DLsdDeXBo6aN4NuM2p/2Y66OqQoJ1o0vsDsCC4b2/R/a2bvXivZ0WA/IfxXlch5P/vx3n7KXNulL08iujI1Ci975jvKk=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=gY8xDospNcdVZXm4R1QgEsAd9Ubdki8nTQzvaAy65o+lJt6O/kN8cqY6FlwsrGO3lA+ad538PcAhiK9pEJOCOZnsJdyadm+6pAsNFTnvXFsfxMPAs2CKQCkvUQYFjeQvu3QSIB9zv6jpx+0uEuJe5ppM4AMneluEMvmxwAH1b90=
Received: by 10.141.123.4 with SMTP id a4mr1828127rvn.294.1204786333288;
        Wed, 05 Mar 2008 22:52:13 -0800 (PST)
Received: by 10.140.171.8 with HTTP; Wed, 5 Mar 2008 22:52:13 -0800 (PST)
Message-ID: <88f5d710803052252k38e0624ja0f4f02e9aec723b@mail.gmail.com>
Date: Thu, 6 Mar 2008 06:52:13 +0000
From: "Paul Fremantle" <pzfreo@gmail.com>
To: user@synapse.apache.org, dev@synapse.apache.org
Subject: Re: Synapse proxy service with slashes not working. Ideas for
 versioning web services at url/endpoint using synapse?
In-Reply-To: <672a01200803051026r188241e4p32870c832f6fb795@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <c2fb3a880803050958s6727eba9lf1c788db5e9febfe@mail.gmail.com>
	 <672a01200803051026r188241e4p32870c832f6fb795@mail.gmail.com>
X-Virus-Checked: Checked by ClamAV on apache.org

I think we need to improve Synapse (and Axis2) to support this model.

Paul

PS  In fact, I'd really like to see Synapse allow exact URLs to be specified:

for example

<proxy name="blah>
   <url="http://server.com/myurl/2008-09-09/service">
   ...

</proxy>

On Wed, Mar 5, 2008 at 6:26 PM, Ruwan Linton <ruwan.linton@gmail.com> wrote:
> Hi john,
>
>  This is expected, even though Synapse proxy services lets you create a proxy
>  with the '/' character, it is a special character for the URL based
>  dispatching because it breaks the splits the String representation of the
>  URL from the '/' character to find the service. Due to the presence of the
>  '/' in the name of the service, URL based dispatcher will not be able to
>  dispatch this because it only sees the version number as the service name
>  after the splitting.
>
>  Workaround for this is either to eliminate the '/' character and use some
>  other character instead or send the version as a parameter, for example
>
>  http://synserv/soap/2007-10-10/MyService ==>
>  http://synserv/soap/2007-10-10_MyService<http://synserv/soap/2007-10-10/MyService>
>  or
>  http://synserv/soap/2007-10-10/MyService ==>
>  http://synserv/soap/MyService?<http://synserv/soap/2007-10-10/MyService>
>  version=2007-10-10 <http://synserv/soap/2007-10-10/MyService>
>
>  Even here for the second case you will have to use a router inside the
>  mediation to decide the correct service, but this approach is more towards
>  the HTTP semantics.
>
>  Will it be possible for you to use one of these strategies?
>
>  Thanks,
>  Ruwan
>
>
>
>
>  On Wed, Mar 5, 2008 at 11:28 PM, J Bouck <bouck.dev@gmail.com> wrote:
>
>  > I would like to use synapse to make available several versions of a
>  > web service available at the same time in the same synapse server.  It
>  > would seem to me that a logical way to version the web services is by
>  > date of deployment.  I would like to define synapse to have proxies
>  > defined like:
>  > http://synserv/soap/2007-10-10/MyService -> version 1 of the service
>  > http://synserv/soap/2008-01-10/MyService  -> version 2 of the service
>  > http://synserv/soap/2008-03-05/MyService -> version 3 of the service
>  > I know that I could do content-based versioning
>  > (http://wso2.org/library/2611), but I feel that versioning at the
>  > url/endpoint is the simpler solution.  Synapse 1.1.1 will let you
>  > define a proxy service called "2008-03-05/MyService",  but at run-time
>  > and discovery it does nothing but Accept (202) or redirect (302) you
>  > to the http://synserv/soap location.  It seems like a bug to me.
>  > Synapse or Axis2 doesn't seem to like services with a slash (/) in
>  > them like:
>  > <proxy name="2008-03-05/StockQuoteProxy" transports="https">
>  >      <target inSequence="inbound" outSequence="outbound"
>  > faultSequence="textfault"/>
>  >      <publishWSDL
>  >
>  >  uri="file:repository/conf/sample/resources/proxy/sample_proxy_1.wsdl"/>
>  > </proxy>
>  >
>  > Any suggestions on a url-based versioning scheme that can be done with
>  > synapse configuration?
>  >
>  > ~john
>  >
>
>
>
>  --
>  Ruwan Linton
>  http://www.wso2.org - "Oxygenating the Web Services Platform"
>



-- 
Paul Fremantle
Co-Founder and VP of Technical Sales, 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

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@synapse.apache.org
For additional commands, e-mail: dev-help@synapse.apache.org