• Post Reply Bookmark Topic Watch Topic
  • New Topic

Web Sevice vs Web Application  RSS feed

 
k mayank
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Friends,

I have been trying to find the difference between Web Sevice and Web Application.

While the link below describes it a bit clearly:

http://forums.devshed.com/dev-shed-lounge-26/web-application-vs-web-service-63625.html

What I wanted to know is that
1) if I have a servlet appplication which takes request in xml form(POST) and responds again in xml form, can it be called a web service.
2)What if i just take xml request and respond in plain text(no xml form), as what user might be interested is just some responce code.

3)Or is it mandatory for a application to use SOAP, UDDI or WSDL to be called a web service.
4)Is every web service a web application.

Please help me clear these doubts I have.

Regards,
 
Sandeep Kumar Jakkaraju
Ranch Hand
Posts: 75
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Mayank .... very nice post ......

I would also like the clear answers for this .....

You need a server like axis.... which helps you expose your method as web service ...
You need all the components I guess to be called as web-service ....

If you have a web-service ..you can have any client (WS) access it !!! irrespective of the technology whether it is MS or Java

You send xml and receive xml ..u need a specific client ..which knows that xml dtd !!! dont you ...

Thats my 2 Rupees about WebService !!!

I cant make comments about the performance yet .....
 
Peer Reynders
Bartender
Posts: 2968
6
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
k mayank wrote:4)Is every web service a web application.

Currently I would say yes. For example, the Web Application Description Language (WADL) describes a non-SOAP web service, yet deals with it as a web application.
However it wouldn't suprise me if some years down the road a true "web" application would have to conform to the Representational State Transfer style inherent to the "World Wide Web" architecture. If that happens, RPC-style services (which would include SOAP web services) couldn't be considered true true "web" applications or true "web" services.

3)Or is it mandatory for a application to use SOAP, UDDI or WSDL to be called a web service.

No - but the problem is that many people see "web service" and automatically assume "SOAP web service". In many contexts capitalization matters and "Web Service" means SOAP web service. However the only way to avoid confusion is to be specific - i.e. don't simply use "web service" but establish clearly what type of web service you are talking about, e.g. SOAP web service, RESTful web service, POX over HTTP web service, etc.

1) if I have a servlet appplication which takes request in xml form(POST) and responds again in xml form, can it be called a web service.

Yes - that is typically referred to as a "POX over HTTP web service" (POX - Plain old XML).

2)What if i just take xml request and respond in plain text(no xml form), as what user might be interested is just some responce code.

That is possible too - however the IANA MIME Media Type in your response Content-Type header for case (1) should be application/xml while in case (2) it would most likely be text/plain. You may also want to consider the possibility of content negotiation as some HTTP clients may prefer text/plain while others prefer application/xml.

In any case there is a pretty good chance that neither case (1) or (2) conform to the Representational State Transfer style inherent to the "World Wide Web".
 
k mayank
Greenhorn
Posts: 27
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Hi Peer,

Thanks for your reply.
This has made my doubts a lot clear.
Thanks again.

Regards,
Mayank
 
  • Post Reply Bookmark Topic Watch Topic
  • New Topic
Boost this thread!