<< 1 >>
Rating: 
Summary: Good coverage and well laid out.
Review: I am a big reader of tech manuals and as such I think that I have a good frame of reference when it comes to computer tech. manuals. This book is very well presented and laid out. The concepts are illustrated by examples and the text does not wander off into details that can easily be had on the web. The whole point of these books is to distill(clarify) the information that is available online. This book gets you up and running quickly.Stef
Rating: 
Summary: fustrating
Review: I haven't finished the book yet but found it confusing. The examples are not completed, the reader doesn't have an example of the completed exersize. The author assumes the reader is using apache and tomcat servers. I don't know anyone using them, most developers I know use windows 2000 or NT, running IIS. JDOM is still beta and there's a whole chapter dedecated to JDOM, where it could have been spent on explaining SAX and DOM in further detail by applying useful simple examples. Overall I'm not impressed with the book. Better to read it at the book store and look for something better to purchase. Look for a text that uses IIS and not tomcat and apache, unless you are running those servers. This is not a beginners book, also purchase a JAVA/JSP text.
Rating: 
Summary: There exist better books than this!
Review: If you are a "from scratch" reader, then choose another book, because this one tries to teach you too many things in a few words (XML, XSL, Xwhateverelseyouwant, DTDs, Java and OOP basics, JSP, JDBC, even some SQL, Server side programming, etc...). Otherwise, if you already know Java and JSP, this book could be helpful to you in understanding what XML is, but you'll find it spends lots of words in explaining useless things about Java that you already know, and it doesn't give any reply to the question: "How XML and XSL can be used to separate content from presentation?". The author uses XSLT mainly to dynamically build different XHTML pages (with different contents, but the same presentation) starting from a single XML file and a number of XSL files. From the developer point of view, what is needed is just the opposite: the developer writes a program that outputs a number of XML files, the designer builds a single XSL file and the server mixes up the files and produces the XHTML output. The fact that XSL is (nearly) powerful enough to substitute a programming language is not a good reason to use it for that!
Rating:
Summary: Good Concept, but
Review: In my opinion, The concept would have been good if the content was not so inept. The source code that was associated with this book was dismal, virtually useless. Many times the source code would not give the results in the book, so I found myself doing more trobleshooting than learning. Both Que and the author should be ashamed of distributing such an inferior product.
Rating:
Summary: Great book , but not really a intro book
Review: The pace of this book was its best feature, starting with HTML and CSS and then slowly adding in XML & XSL before jumping into the enigma of server side transformations using Java. You may want to pick up "Java 2 From Scratch" or another intro to Java book prior to reading this. I think this book was a great attempt at fusing two complex languages and sets up a good foundation to move on to more detailed books.
Rating:
Summary: Excellent if you already know server-side Java!
Review: The title of this book seems to imply that it is meant to teach you both Java and Xml in one go, but you really need to have already done some serious Java programming and particularly have a few servlets under your belt. It an excellent book for those who wish to learn the specifics of using Java to read and write Xml. It takes you by the hand and shows you how to turn your servlets into applications that can turn XML into any format for the web or B2B using SAX, DOM, JDOM in Java programs to take advantage of the power of XSL, XSLT and XSD.
Rating:
Summary: Clearly Explained
Review: This book is an excellent introduction of XML, as well as XSLT, XSLFO, in conjunction working with Java and SOAP. It clearly explains the fundamental concepts one needs to build a strong foundation. In learning a developer can see how XSL could replace JSP. This will definitely be an interesting battle to watch.
Rating:
Summary: Don't be amazed by this book.
Review: This book tries to cover so many things at once --XML, Java, DB concepts, tools, Servlets, -- that it ends up teaching technically nothing. About half the contents of the book are XML non-related stuff. The author tries to cover such a programming language like Java in 470 pages of so many things, that he even does some bad practice! For example, he starts teaching a way of reading the contents of a file in Java, and two pages after the example he explain the Exceptions issue. If you're a Java newbie, you'll be on a big trouble unless you read the whole chapter before typing anything. The author even tries to explain the relational database concept by ilustrating it with an Excel sheet! I must confess that this book covers just the basics, since it wastes too much time in things it can't cover. This book would be better if it talks about XML only, and leaves Java and other subjects to the pros. If you want to "get serious" (like the author says), then buy a book that goes deep into this matter, a book that doesn't talk about everything just to mention a bit of each.
Rating:
Summary: TERRIBLE
Review: This book trying to cover everything among three-tier design within 470 pages, which is impossible. In order to understand this book, I need to read other books, like "Javaservlet" and "Beginning XML". But after I finish those reading, this book is not necessary anymore, so why wast time on this book? Some of the programs in this book are not executable and even worse.....some figures (screen shot) are misplaced.
My opinion of this book is "terrible"!
Rating:
Summary: disappointing
Review: trying to cover too much, this book ends up getting too much involved in covering the furniture example and fails to explain the concepts of xml as well as java. I think it would have been much better if the writer had tried to target either java or xml and not both and end up mixing everything. It surely is no good for 'from scratch' readers.
<< 1 >>
| 
