- Packt Publishing
- Publication date:
- Product dimensions:
- 7.50(w) x 9.25(h) x 0.67(d)
Most Helpful Customer Reviews
See all customer reviews
Spring Web Services Cookbook based on 0 ratings. 3 reviews.
I’m reviewing this book thanks to the good people at Packt publishing that give me a PDF copy to read I’m a SpringSource Certified Instructor and Spring WS is one of the most difficult part to teach en every course. And not because the framework is complicated, is the technology (SOAP) that is very complicated. So, having a book in the topic at hand is a very good thing. First of all the good parts: -This is the first book on Spring WS and do a very good work covering every corner case. Is, by far, more complete than the official documentation -And when I say “every corner case” is TRUE (seriously, the whole enchilada), from things like using XMPP to send a SOAP message to secure a WS using WSS4J, including Spring Security and many more things. -The book also cover Web Service with REST (without covering security ) and Spring Remoting Now, the (very minor) bad parts: -This format (a Cookbook) is not the best way to teach topics in a deep way -The code looks horrible (at least in the PDF version) and is very hard to read. This is epidemic in other Packt publishing books (Hey Packt’s friends, take note). Reading the code from the example code is better, but, the code have little or no documentation at all and is poorly formated. -The implementation details in some examples aren’t the best. The use of some deprecated classes, building new instances just to call static methods, using XPath without XPathOperations (a nice interface that define some very helpful XPath methods) and so on -In the Spring Remoting part the authors don’t cover HttpInvoker that is the more natural way to communicate two Spring applications. (In fact HttpInvoker is nicely cover in the Spring documentation, so is just a matter of taste) In conclusion This a very good book, the authoritative reference for Spring WS
This book starts with a brief introduction of how the Spring handles Web Services, and follow by various description to configure and build a Web Services in Spring. On top of that, it provides a simple, precise and working example, while some books lack of those. There are some basic topics that the author did not cover it, such as manipulating the SOAP Headers, attachment, etc. These may give the book a complete coverage of basic Web Service in Spring. I would recommend this book for someone who is looking for a quick reference to build Web Service in Spring fast.
In general, this book is definitely a spring-web services recipes for beginner, in a high level which a bunched examples using 2 main things: spring + web-service. For my perspective, It's oriented for beginner users who wants start to considerer spring which one way to implement web-services but in my case I'll expected more advanced scenarios and dig deeper into both technology. Apart from that there are some improvement points that I'm mentioning below: * I suggested add an introduction in web service and every specification involved like UDDI, SOAP, WSDL, JAX-RPC/JAX-WS. * I suggested add in every recipes why should be good implementation in that way. * I suggest add a chapter for SCM and versioning of web services. * I suggest add a chapter with most of important classes mentioned in the book with a briefly explanation. * I suggested add an introduction of concept of each recipes examples mentioned in the book too. * I suggested review some chapters against: o Chapter1 and Chapter2 add more references and better explanation. o Chapter4 o Chapter7 : It need a clear comparison about which converter is most suitable in each case according performance, interoperability, extensibility, o Chapter9: It should be outside the main chapter of the book, could be an extra chapter at the end of its to introduce us rest service with spring. Apart from that, there are some parts wich need revision against or add more explaination more about: handler, resolver, exception, converter, media type, content-negotiation and so on. * The examples NEED pay attention about code formatter because it's poor. * The example and command we must ensure that it's run properly like we referred in the book. * The examples also need to add comments and more clear explanation about how can we run, especially thinking in another scenario than default. For example in each example say: run this command line: "mvn .... Tomcat:run" but this case expected everything run properly in default port 8080 but should be considered how someone could change and run in different port or another configuration.