At the end of the day, Web services is not difficult to draft. In the Java language, writing Web services requires an understanding of at least half a dozen specialized APIs, and more than that if you want to do anything fancy.) Java Web Services is not a very good job Dispersing confusing terminology (and obfuscating hype and show you how to do Web services work in Java. David Chappell and Tyler Jewell have comfortably get into less than 250 pages what others do not do as well in twice as much space. Take Universal Description, Discovery, and Integration (UDDI) work as an example. Similarly pragmatic attention goes to Simple Object Access Protocol (SOAP), where they show how to create a message, fill it with XML, create an attachment if necessary, and send it in transit. You will not find many frills explanations or conceptual (though there are enough "why" part to make sure that you are not just typing recipes blindly), the emphasis is on writing Java code that interacts with the protocol and standard web services. - David Wall Topics covered: How to write Web services software in Java, in connection with the Universal Description, Discovery, and Integration (UDDI), Simple Object Access Protocol (SOAP) and Web Services Description Language (WSDL).