- Paperback: 320 pages
- Publisher: O'Reilly Media; 1 edition (February 22, 2009)
- Language: English
- ISBN-10: 059652112X
- ISBN-13: 978-0596521127
- Product Dimensions: 7 x 0.7 x 9.2 inches
- Shipping Weight: 15.2 ounces
- Average Customer Review: 32 customer reviews
- Amazon Best Sellers Rank: #1,379,059 in Books (See Top 100 in Books)
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.
Java Web Services: Up and Running Paperback – February 22, 2009
There is a newer edition of this item:
Customers who bought this item also bought
What other items do customers buy after viewing this item?
A quick, practical, and thorough introduction
About the Author
Martin Kalin has a Ph.D. from Northwestern University and is a professor in the College of Computing and Digital Media at DePaul University. He has co-written a series of books on C and C++ and written a book on Java for programmers. He enjoys commercial programming and has co-developed large distributed systems in process scheduling and product configuration.
Discover books for all types of engineers, auto enthusiasts, and much more. Learn more
Top customer reviews
There was a problem filtering reviews right now. Please try again later.
The author also appears to ignore other common industry practice or industry norm. E.g. in the RestfulTeams service (page 137), information about the new team to create is contained in the HTTP header rather than in the body of the HTTP request to demonstrate "the flexibility of REST-style services".
While it is interesting to show it is possible to develop a Dispatch client against a SOAP based service with HTTP_BINDING (page 158), the author does not even mention the better, easier and more concise alternative, i.e., to use the default SOAP_BINDING for the Dispatch client.
Section 5.3.2 HTTP BASIC Authentication (page 212) is another example of abusing a well defined and well understood IT industry terminology, while the true HTTP BASIC Authentication (on Tomcat) is covered under another section (page 219, Container-Managed Authentication and Authorization) without explicitly lableing it as such.
Overall, the first 120 pages is a good introduction to JAX-WS 2.1. The rest of the book appears to be filler from various lecture notes.
After being trained to read books (as opposed to code) sequentially for years in the public education system, readers don't expect to see references to things they've not yet encountered. Problem here is context switching, i.e. the same reason IDE's have all these built-in widgets and plugins... so the developer doesn't have to switch contexts mentally in order to get something besides coding done. A subversion check-in for example. So I'm reading along and I find a reference to an object I've not read anything about so far in a code example. Where did I miss that? The reader now has to thumb backwards in order to find out that the writer hasn't introduced the object of consternation yet.
My point is that a writer should never do this. If the reader reads a code example and there is a reference to an Object, method, etc. the reader should already have read the declaration and implementation of that object or method so that they don't trip over something that seems to be a mystery and have to switch contexts in order to figure it out. Style is not nearly as important as clarity or understanding. To top that off, "style" in the reader's shop is probably different from "style" in the writer's shop anyway. So you might as well write it in the clearest and most understandable way anyhow.
Another pet peeve of mine is that the code examples are non-functional which is to say that if you go and download them, there is no build. Would this really have killed the author?
I think the objections to the book might be the "Up and Running" in the title. It is more about "Under the Covers".