Sorry to say but the article listed below is very misleading. Comparing REST vs SOAP is the same as apples vs oranges. REST is an architectural style while SOAP is just a message format. REST vs WS-* or SOA in general is a more meaningful comparison. All though there are quite a few folks who think REST is one way to realize SOA.
For most folks REST means XML over HTTP/GET which is not correct at all. Read this blog post by Sanjiva http://www.bloglines.com/blog/sanjiva?id=227to get a more balanced view. It is important to understand that in order for your service to be RESTful your service needs to obey the REST constraints. Flipping the switch "disableREST" doesn't make your service RESTful or not. All it does is to change the message format from POX to SOAP. You have a greater responsibility to ensure that you design your service in such a way that it obeys the REST constraints. Regards, Rajith Attapattu. Red Hat. On 10/9/07, Ganesan, Chandru <[EMAIL PROTECTED]> wrote: > > > Hi > > I'm newbie to Axis, so pardon my rudimentary question? > > What factors should I consider before choosing between REST vs SOAP > request processing in Axis 2.0? > In case of SOAP I'd use axis2/services URI path in the WSDL soap port > (AxisServlet) > In case of REST I'd use axis2/rest URI path in the WSDL soap port > (AxisRESTServlet) > > If you could also provide some basic info on the difference between REST > and AXIS request processing, it w'd be very helpful > > > thanks > Chandru Ganesan > HP Select Identity > 972.497.2403 (Work) > 3000 Waterview Pkwy > Richardson TX 75080 > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
