| Welcome to vBulletin FAQ |
vBulletin FAQ Navigation
Getting Started
Customizing your vBulletin
Search Engines & SEO
Making Money with a Forum
Promoting your Community
|
| Get your own vBulletin Today |
|
| Webmaster Help |
|
|
|
SOA Using Java(TM) Web Services
vBulletin Book Store > vBulletin books beginning with S
|
SOA Using Java(TM) Web Services |
Author: Mark D. Hansen
Published: 2007-05-19 |
List price: $54.99
Our price: $44.78
|
Usually ships in 24 hours
As of: December 02nd, 2008 09:42:09 PM
|
|
|
Customer comments on this selection.
 A great and very difficult SOA book
I've read all of the reviews here, which are interesting and provocative. The ironic thing is that I agree with much of what the one and two star reviewers said but still rate this book 5 stars.
br /
br /Potential buyers need to know what they are getting. This is the single best book on JWS programming available. It's incredibly dense. The acronyms fly all over the place. Hansen dives into technologies and if you don't know the technologies already you will find yourself spending hours digging into things like XSLT. We're talking about many, many hours to swallow the whole thing. It's an expert's book - anyone who is serious about JWS and SOA has to have this book with Monson-Haefel 'J2EE Web Services' right next to it to cover the stuff Hansen doesn't address.
br /
br /But I also recommend the book to people who are less serious and have less time, and even to beginners. These readers should buy the book, start with section 7.7 (an excellent demo of the Java 6 Endpoint class, which is as simple as JWS gets), and maybe do Chapter 3 to learn something about REST (also fairly simple). Then put it on your shelf until you have a few hours free, and tackle a section of one of the chapters. Keep at it, though it might take a while. This book will improve your understanding over time. I've encountered a few technical books which I've worn into a limp condition from reading and re-reading - this looks like another.
 Good book, too fine grained project distribution
This book can be really good if you are used to work with maven and ant, otherwise it will be hard to follow. So if you are the kind who likes and best understands things by putting your hands on source code, I'd recommend getting a grasp on the mechanics of maven first, otherwise you'll be struggling with the book contents as well as with maven gimmicks.
br /
br /I personally like to import maven projects into eclipse to dive in the source code, but since eclipse does not support "project nesting" I have to create a new project for every example. Take chapter 3 for instance:
br /
br /It has 4 subdirectories:
br /
br /eisrecords
br /rest-get
br /rest-post
br /xslt
br /
br /Inside rest-get for instance there a 4 maven projects, 2 for services and 2 for their respective clients, and they all have 1-2 classes.
br /
br /The projects work fine once you have set up your environment properly, however I'd much prefer that every project was put into a single unit (on a per chapter basis) with proper pure ant tasks - which in some cases wouldn't be so hellish to code because there aren't that many dependencies to manage, but still, using maven to build is less error prone.
br /
br /Other chapters are indeed built as maven modules which makes it easier to import to eclipse but still, it's not cool having to deal with so many projects for such small examples.
br /
br /I personally like the writting. I'm still on chapter 5 but so far it was the best book on the subject I could find. It goes beyond hellowordish examples and is filled with code which can be "easily" tested.
 SOA using Java Web Services
I'm a Java developer with 5 years experience. I wasn't looking for a beginners book, but certainly I wanted one that could give me the big picture of SOA. I think the author is an expert (as all authors should be) and he knows what he's talking about, but overall I think he's a subpar writer (in the context of writing computer books) and the book is organized poorly in my viewpoint. There's way too many acronyms in the book and the chapters are long! The book has a very "wordy" feel to it. His explanations are not "pointed" and he often injects too much extra information the just ends up confusing the reader. For example, he loves to bullet point subjects in order to create talking points. The problem is, however, each bullet point is a huge block of text and it tires out the reader. He may have 10 bullet points each with 15-20 lines of text. Don't get me wrong, he stays on topic, but he says too much. Any technical writing expert will tell you this is improper for using bullet points. Each bullet point should contain just a few lines of text. ... I think only if you are an expert SOA Architect you can get a lot out of this book. If the talking points could be just a little more brief, it could be a better book. If you are new and just want to get the big picture, you will feel lost and overwhelmed.
Terrible writing
Author says that there are many tutorials how to create a 'hello world' webservice but when you want to create a bigger system it is not that easy. I think that when you write a book you should start from a hello world example and than explain more complex solutions. What is more, I think web services are not difficult. This book makes it difficult.
br /Summing up, this is terrible writing. I don't like it.
Does a good job explaining a complex topic
Java Web Services and SOA are difficult to learn. It is not the kind of hard that learning partial differential equations is, where once you have a concept down you can solve any problem of that type. It is a different kind of hard, the kind of hard that comes with solving a distributed computing problem. After all, that is what SOA and web services cover. Thus given a spider-web of a problem and spider-web of tools to solve it, you can't expect a turn-the-crank solution to your problems. The author does do the best job I've seen of making sense of the programming part of SOA.
br /
br /This is not a book that covers the concepts and design philosophy behind SOA. For a good introduction to SOA from a Java perspective I recommend Service Oriented Architecture with Java. This is a great book for the Java developer who already understands the concepts of SOA and wants to learn how to design Web Services and implement SOA from a Java perspective.
br /
br /Chapters 1 and 2 review the Java Web Services (JWS) standards in detail and describe how they improve on the previous set of JWS standards. Chapters 3 through 10 focus on writing code. To really understand the power and ease of use of the new Java Web Services you must write code, and that is primarily what this book is about. Those eight chapters are packed with code examples showing you how to best take advantage of the powerful fetures, avoid some of the pitfalls, and work around the limitations. Chapter 11 looks to the future and offers some ideas, along with a prototpe implementation for a WSDL-centric approach to creating Web Services that might further improve JWS as a platform for SOA.
br /
br /The book assumes you already have a working knowledge of Java and a basic understanding of XML and XML Schema. You don't need to know much about SOAP or WSDL to begin here.However, you will probably find additional references on WSDL helpful if you want to firm your grasp on some the Web Services basics. The book helps out here by offering its own suggestions for books and websites that have been pretty helpful. The part of Java that you must know in advanced is specifically J2SE 5.0 and the Java language extensions generics and annotations.
br /
br /Finally, be assured that the author will not try to convince you that Java Web Services is easy. He basically sums up the five stages of grief when dealing with JWS
br /1. Denial - It's simple Object Access Protocol, right?
br /2. Over involvement - OK I'll read teh SOAP, WSDL, WS-I BP, JAX-RPC, SAAJ, JAX-P specs.
br /3. Anger - I can't believe they made this so hard!
br /4. Guilt - Everyone else is using Web Services, it must just be that I'm missing something.
br /5. Acceptance - It is what it is, Web Services aren't simple or easy.
br /
br /Expect to take some time in working through this book. It won't just come to you overnight.
|
Similar Listings
|
|
Our vBulletin book picks:
|
|
Find more vBulletin related products of interest.
|
