Thanks for the replies Andreas and Asankha. From these responses I'm getting the impression that Synapse is not really setup to support RESTful services - is this an incorrect read? I'd really like to use the built-in Synapse mediators (particularly throttling) with REST services, but I'd like to know that Synapse fully supports (or will in the near-term) the proxying of REST services and mediation/transformation of same. Is this something that is high on the priority list for the next release(s)?
Thanks again for your insights... Mike -----Original Message----- From: Andreas Veithen [mailto:[email protected]] Sent: Saturday, February 14, 2009 2:08 AM To: [email protected] Subject: Re: Problems with Synapse REST proxy For the blocking HTTP transport, this issue was solved in WSCOMMONS-405. We should realign the behavior of the NIO transport with this. Andreas On Sat, Feb 14, 2009 at 06:52, Asankha C. Perera <[email protected]> wrote: > Hi Mike >> >> My understanding from https://issues.apache.org/jira/browse/SYNAPSE-365 >> and https://issues.apache.org/jira/browse/SYNAPSE-412 is that I can >> setup a RESTProxy and call that proxy - essentially as a passthrough and >> expect the same response as if I had invoked the REST service directly. >> I have a fairly simple GET on a resource that returns an xml response if >> I call it directly, but if I attempt a GET on the resource through my >> Synapse Proxy, the Response is a 301 - Moved Permanently. I'm hoping >> that you can shed some light on what I might be doing wrong. Thanks! >> > > This seems like a bug, where the request did not get dispatched to the > service, and hence a redirect to the service list page instead.. I think we > need to fix the existing JIRA's and ensure good support for REST > > cheers > asankha > > -- > Asankha C. Perera > http://adroitlogic.org > > http://esbmagic.blogspot.com > >
