There is lot of confusion over the webservices.
what are the webservices?
why we go for this extreme technology.
First of all let me suggest you that
webservices are implemented on SOA technology
so i want you to take a look at SOA
and then go for webservices otherwise you will go mad.
if you know XML that would be great advantage
With all due respect, this is an odd post. While I could go to great length discussing each part of it, Ill just briefly mention some of its stranger assertions. Hopefully, amit daundkar won't be too confused by it.
There's nothing extreme about web services. It's a mainstream technology.Web services are not "implemented using SOA technology", it's just the other way round - SOA is an architectural concept, and web services are one way to implement it.Thankfully, the hype around SOA has largely subsided. It is decidedly not necessary to know much about SOA in order to start developing web services (although it may be helpful, but it could confuse more than help).While XML is used in many web services, it is often hidden underneath an API layer (like JAX-WS), so the developer doesn't generally have to be aware of it. The SOAP protocol makes extensive use of XML, but these days REST is also widely used, and it doesn't necessarily use XML at all; its response may consist of JSON, for example.I recommend to start by getting a firm grip of the SOAP and REST styles of web services; the WebServicesFaq has some very useful links about that.
