I am planning to implement web services (Producing and Consuming) both Top down and Bottom up. Does anybody know any good tutorial on it?/ I can Google it and find out myself but I wanted to know from you guys if anything really helped for you.
Web services are such a huge topic these days that there's no single tutorial that covers it all. The http://faq.javaranch.com/java/WebServicesFaq page links to a number of books you may want to consult; in particular check out J2EE Web Services for the basics and SOA Using Java Web Services for the latest in Java web services. [ November 24, 2008: Message edited by: Ulf Dittmer ]
Originally posted by Arjun Reddy: I am planning to implement web services (Producing and Consuming) both Top down and Bottom up.
This seems like you are looking for a more tool-driven (IDE) approach which neither J2EE Web Services or SOA Using Java Web Services will deliver. If anything most web service "enthusiasts" will recommend a more hands on/down in the dirt approach because wizards will often hide details that are pertinent to achieve understanding.
Which really brings me to the core question: Why are you interested in SOAP web services now?
If application access over the web is your main goal then you may want to skip SOAP for now (and only do as much as you have to) and focus more on the more web-oriented RESTful Web Services which are getting technical support now. They are not a silver bullet - however they utilize the web more effectively compared to SOAP web services. The downside is that RESTful development usually requires "an adjustment in developer thinking" which cannot be gained from fiddling with IDEs and APIs.
If interoperation between .NET and Java right now is your goal, you are pretty much stuck with SOAP web services - at this point it is difficult to predict when that will change. The knowledge contained in J2EE Web Services or SOA Using Java Web Services is pretty detailed - however this type of knowledge is essential when diagnosing why some SOAP web service clients and services have interoperability problems.
If you are simply looking for "some type of interoperability" then it can be difficult to choose an optimal approach. Many choose SOAP because of the convenient code generators. Then again, if SOAP is so great why doesn't it have "top dog" status over at a place like Amazon Web Services?