- Paperback: 214 pages
- Publisher: O'Reilly Media; 1 edition (May 2002)
- Language: English
- ISBN-10: 0596002785
- ISBN-13: 978-0596002787
- Product Dimensions: 7 x 0.6 x 9.2 inches
- Shipping Weight: 12.3 ounces (View shipping rates and policies)
- Average Customer Review: 7 customer reviews
- Amazon Best Sellers Rank: #3,495,214 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 and XML Data binding 1st Edition
Use the Amazon App to scan ISBNs and compare prices.
All Books, All the Time
Read author interviews, book reviews, editors picks, and more at the Amazon Book Review. Read it now
Customers who viewed this item also viewed
About the Author
Brett McLaughlin has been working in computers since the Logo days. (Remember the little triangle?) He currently specializes in building application infrastructure using Java and Java-related technologies. He has spent the last several years implementing these infrastructures at Nextel Communications and Allegiance Telecom, Inc. Brett is one of the co-founders of the Java Apache project Turbine, which builds a reusable component architecture for web application development using Java servlets. He is also a contributor of the EJBoss project, an open source EJB application server, and Cocoon, an open source XML web-publishing engine. He is author of the soon-to-be-released O'Reilly book, Building Java Enterprise Applications.
Top customer reviews
The brief mention of JAXB ( 4 pages ) is only philosphical. Even that is w.r.t. an obselete version with DTD support.
( Current JAXB only supports XML schema )
An excellent example of this approach can be found in "More servlets" by Marty Hall.
As for this book, I find it useful to grasp general concepts, but not as a detailed technical discussion it appears to be.
Sample code for chapter 3 is useful, but then we need a sample to actually compile and run some simple JAXB example. Unfortuantely, there is no way to accomplish this with the code that comes from the books's Web site.
Also, as early as in chapter 4, we have quite a big jump from basic discussion directly to using JAXB data binding in servlets - without any consideration of necessary intermediate steps: checking Tomcat configuration, running JAXB-free servlet examples, making servlet-free JAXB examples work, etc.
Needless to say, JAXB and other XML binding frameworks are useful for servlet development, but they are also useful
for JSP and other XML applications. From the other side, servlet parameters can be accessed using regular application server configuration features like it is done in Tomcat EXAMPLES app. All these considerations are completely missing from the book.
Besides poor sample code and appplication server discussion, another source of confusion is the absence of proper references to XSLT. In fact, the purpose of XML data binding is to enable Java program to work "like" an XSLT transformer, in principle, XML document processing can be done by XSLT. Again, reading the book there is no way to figure this out.
Excellent treatment of JAXB data binding is available online from IBM Web site, see Daniel Steinberg's tutorial. I'd also suggest Java Web Services Tutorial from Sun.
However I am a little disappointed because the author has taken a biased look at data-binding. He has not mentioned the drawbacks of data-binding in a single place. Obviously there are many drawbacks of such a approach. One of them is that your once independent data-containers are now tied to a framework. Secondly if there is a small modification made to the xml, the classes have to be re-generated and you end up with two code bases. Such issues are not mentioned in the book.
The least I would expect in such a detailed book when different frameworks are compared side by side is a comparison chart that I can refer quickly.
I give a four star rating because it contains a lot of detailed information about the data-binding framework but failed to tell why data-binding might not be the right solution.