Service Oriented Architecture with Java: Using SOA and web services to build powerful Java applications Paperback – 26 Jun 2008
|New from||Used from|
- Choose from over 13,000 locations across the UK
- Prime members get unlimited deliveries at no additional cost
- Find your preferred location and add it to your address book
- Dispatch to this address when you check out
Enter your mobile number or email address below and we'll send you a link to download the free Kindle App. Then you can start reading Kindle books on your smartphone, tablet, or computer - no Kindle device required.
To get the free app, enter your mobile phone number.
About the Author
Vincenzo Caselli graduated in Electrical Engineering in 1991 at the University of Bologna. Since 1996 he has been working as an independent consultant and Java trainer for several Italian software houses. He began working as a developer in Delphi and other visual IDEs with AS/400-based companies. Soon he shifted his focus to Java and began to propose Swing client/server multi-layered solutions to his customers. He also worked in the web development area with several frameworks (Struts, Hibernate, Spring, JSF, and GWT) in different fields (banking, manufacturing, healthcare, and e-learning). Recently he collaborated with IBM in projects based on Eclipse RCP and SOA. He is interested in every consultancy and training activity aimed to improve the productivity and quality of the software development process, possibly by using open-source products.
Top customer reviews
Most helpful customer reviews on Amazon.com
. If the aim is to learn about JAX-WS, JAXB, WSDL, SOAP etc in more detail than a reading it off a billboard then this book is not for you. This was akin to reading a ppt or off a billboard. Yes, there was some useful information but it was more like a pointer that I had to follow through with the aid of google.com to get comfortable with it. This book will give you a lot of jargon in 175 pages but that is about it. And it will also make your wallet lighter. I could have used the JAXB tutorial on the JAXB net site and that would have covered JAXB and I assure you that is awesome. JAX-WS details someplace else. Similarly for SOA, Mike Hansen's book would do the trick. Unfortunately, I would have to agree that the absence of writers such as E Rusty Harold, Monson-Haefel is being felt in the SOA and Java Web Service arena.
. Overall the quality of writing style is confusing and terminology and acronyms are scattered throughout and in some cases, not explained satisfactorily at all. For instance "3GL", "4GL", "M and A" etc. Repetitions galore in 175 pages - start to finish. It would appear as if the content in the book has not been proof-read and the authors have collaborated albeit still have managed to essentially hash the same stuff again and again. This is a book about SOA but does that imply that some SOA aspects have to be repeated again and again? For instance: "Why SOA" in the first chapter 1 and then the same hashup in the last chapter.
I think I would need to go off PACKT publishing for a while as well just for my sanity - this time that I spent on trying to read this book will never come back - all I can do is to write this review and make some positive contribution off that.
1) Fundamentals (SOA + Web services)
2) Code examples (web service implementations + emerging standards)
3) Benefits (Case studies + Goals)
I appreciated the first part where the authors cover the fundamentals and the benefits of the Service-Oriented-Architecture together with a clear explanation about the communication protocols used for the web services (SOAP and REST), the differences between the RPC and Document Based-WS approaches, and the existing implementations for web services (JAX-WS 2, Axis 2, Spring-WS, XFire/CXF 2.0).
The second part is certainly the most practical one. It provides representative code examples about each one of the mentioned implementations (the code is available from the publisher's site) and shows the way each of these implementations work.
And the final part makes a comparison between an Enterprise Application Integration (EAI) approach versus a SOA approach (this last one superior to the first one, of course) and a conclusion about the goals that can be achieved with SOA.
What I think needs to be considered:
1) The last chapter (Goals we can achieve with SOA) is misplaced. It should be part of the introduction and not part of the conclusion. In fact, even the header on this chapter indicates Chapter 1 instead of Chapter 6, which may suggest a last minute change (without the appropriate verification).
2) In the case study with the EAI approach, benefits and drawbacks are mentioned. In the SOA case study, there are only benefits. Is there really not a single drawback for this approach?
3) I would also suggest changing the font used on level-1 and level-2 headers. The difference between them is not evident and this makes it a little bit difficult to see the structure of the chapter.
What I missed in the book:
1) A separate section about additional resources (tools, recommended reading, etc).
2) A mention of standards and/or best practices when implementing web services.
3) A more complete explanation about the way to implement "Contract-First versus Contract-Last approach" when defining a web service. When I read: "(...) creating a WSDL is not a trivial process and hence we may not be able to do that easily without some special tool support." ... and there was no tool recommendation or a short example I felt disappointed.
It is certainly a good introductory book on the subject. If you are looking for an overview on SOA and web services, it is a good point to start.
Look for similar items by category