Mike, I think a realistic view is as follows: - Synapse relies on Axis2 to handle REST (which internally represents REST requests as SOAP); REST support in Synapse is therefore as good/complete as in Axis2. Note that since I'm not very familiar with that part of Axis2, I'm not in a position to give an opinion on its quality. - REST is not entirely transport agnostic. Since Synapse has its own (non blocking) HTTP transport implementation, this means that there can be specific issues which appear in Synapse but that don't exist with Axis2's default HTTP transport (as can be seen from this thread). Note that these issues are in general quite easy to fix. In addition, since the transports are loosely coupled to the rest of Synapse, you can easily replace the HTTP transport component by a newer version. It is just a matter of replacing a JAR file. You also have the option of using Synapse with Axis2's default HTTP transport (though this is not recommended for other reasons). All this means that the risk related to this type of issue is quite low.
To answer your question about the priority of REST related improvements, I think that everything depends on user feedback: If you identify and report REST related issues and provide us with all the info required to track them down, I'm pretty sure that enough people in the developer community will be ready to help fixing them. Andreas PS: BTW, is there already a JIRA report about the issue you described in the initial post? If not, please open one so that we can track that problem. On Tue, Feb 24, 2009 at 08:21, Obendorf, Mike <[email protected]> wrote: > 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 >> >> >
