You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by "Ganesan, Chandru" <ch...@hp.com> on 2007/10/10 00:59:52 UTC
SOAP vs REST request
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: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: SOAP vs REST request
Posted by Demetris G <de...@ece.neu.edu>.
And I second Rajith's response below ... I am surprised that some people
actually found articles about this comparison that does not seem to be
at the same level .. messaging vs a SOA architecture ...
Interesting ...
Rajith Attapattu wrote:
> 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=227 to 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* <chandru.ganesan@hp.com
> <ma...@hp.com>> 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: axis-user-unsubscribe@ws.apache.org
> <ma...@ws.apache.org>
> For additional commands, e-mail: axis-user-help@ws.apache.org
> <ma...@ws.apache.org>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-user-help@ws.apache.org
Re: SOAP vs REST request
Posted by Rajith Attapattu <ra...@gmail.com>.
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 <ch...@hp.com> 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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
int array type is not recognized in .Net client (AXIS2)
Posted by harsha kilangodi <ha...@yahoo.com>.
Hi all,
We have deployed webservices using AXIS 2.0.We are facing problems in .NET client which is unable to recognise the int Array type. Once the stubs are generated (Reference.cs file ) in the .NET client we have tried to assign int[] to one of the request parameters. But it is giving compile time error saying "Cannot implicitly convert int[] to int?[]".
Please help us to solve this problem
Regards
harsha
---------------------------------
Be a better Heartthrob. Get better relationship answers from someone who knows.
Yahoo! Answers - Check it out.
Re: SOAP vs REST request
Posted by keith chapman <ke...@gmail.com>.
Hi,
If you are using the Axis2 1.3 release (If your not better upgrade to that)
you wouldnt fine a seperate RESTServlet. both REST and SOAP request are
handled by the same servlet now. Also as a newbie if you want to have better
REST support I'd advice you to deploy your service via a WSDL 2.0 document
(If you need help I can help you on that), cause WSDL 2.0 HTTPBinding gives
you full control of the request URI.
Thanks,
Keith.
On 10/10/07, Ganesan, Chandru <ch...@hp.com> 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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/
Re: SOAP vs REST request
Posted by Anas Mughal <an...@gmail.com>.
Your question seems to be a generic comparison between REST and SOAP. Good
discussion and comparison could be found thru Google:
http://www.google.com/search?q=rest+vs+soap&rls=com.microsoft:en-us:IE-SearchBox&ie=UTF-8&oe=UTF-8&sourceid=ie7
On 10/9/07, Ganesan, Chandru <ch...@hp.com> 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: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>
--
Anas Mughal