This week's giveaway is in the EJB and other Java EE Technologies forum. We're giving away four copies of EJB 3 in Action and have Debu Panda, Reza Rahman, Ryan Cuprak, and Michael Remijan on-line! See this thread for details.
This week we are giving away four copies of "Professional Java XML", and the Author, Jeremy Crosbie, is on-line! Everyone please give Jeremy a warm JavaRanch Welcome Entry requirements for the Giveaway can be found at http://www.javaranch.com/bookpromo.jsp Jeremy, so which picture on the book is yours?
One of the few criticisms I've seen about big Wrox books is that being written by / contributed to by multiple authors can lead to inconsistencies in coverage of topics and examples used. Just wondering what was the collaborative effort here; were there extra measures taken to create a unified book?
Thanks for the welcome! I am honored to have been asked to contribute to this forum and hope that I can answer or at least provide guidance on how Java and XML can work together. As far as which picture is mine, I am the last picture in the top row ( the far right ).
Jeremy Crosbie<BR>Co-Author of <A HREF="http://www.amazon.com/exec/obidos/ASIN/186100401X/ref=ase_electricporkchop" TARGET=_blank rel="nofollow">Professional Java XML</A>
Joined: Jun 20, 2001
My experience writing for WROX was that it isn't what I would call a "stovepipe" process, meaning that we aren't all left to write on our own. The technical leads for the book did a great job in keeping the authors from covering topics that may be covered earlier or are to be covered in greater detail later. There are pluses and minuses to any book with multiple authors. The minuses, like you state, are that you can end up with a book that doesn't flow properly. On the other hand you get a wide perspective on the topic being discussed. I think the latter works on books that cover Java and XML because it is a wide topic .
Originally posted by Richard Smolen: One of the few criticisms I've seen about big Wrox books is that being written by / contributed to by multiple authors can lead to inconsistencies in coverage of topics and examples used. Just wondering what was the collaborative effort here; were there extra measures taken to create a unified book?
Thomas! I could only hope that Jeremy is too busy answering questions to find this thread... And now what?
Leverager of our synergies
Joined: Aug 26, 2000
Originally posted by Richard Smolen: One of the few criticisms I've seen about big Wrox books is that being written by / contributed to by multiple authors can lead to inconsistencies in coverage of topics and examples used.
Richard, you stole my question Actually, reading Wrox books I had the opposite feeling: that authors somehow manage to keep consistent approach and even consistent writing style, which is a total mystery to me Of course, it can be a result of heavy editorial ironing Negative side IMHO is that Wrox books are less "authors books"; they all are of the same even and usually very high quality, but they all are... predictable, whether it's good or bad. Maybe it's not bad.
Thomas Paul, Great picture! I have read a couple of Wrox books. In general, the flow is ok but there are obvious parts that just seem different (like in coding style for example). But like was already mentioned, it wouldn't really matter since it would be covering a different topic. Wrox does a good job in my mind
This is good promotion. I like it... ------------------ MAC
Joined: Jun 20, 2001
Thank you for the kind words. This was my first effort at publishing and I must say it was a lot of fun. The old saying "the more you know the more you realize what you don't know" was so true during the entire process. My approach is to assume nothing. Even though it is a "Professional" book you wouldn't be writing it if your reader already knew everything. I like to be deliberate and detailed when teaching something new. I hope that comes across when people read it.
Originally posted by ajay sagar: Hi jeremy nice to have you here I was going through your book given to me by a colleague and was facinated by the simplicity of your writing keep up the good work
Hey Jeremy, Do you intend to include some certification oriented chapters in your future realeases? This helps one test his fundamentals and even make them stronger. Something similar to what Philip Heller wrote in his book authored for Java certification study.
------------------ abhijit from pune. Ability alone is not enough for success,it must be sparked by ambition and sustained with determination
<b><i>Abhijit</i></b> <br />---------------------------------<br />Give me my share of smile!
Joined: Jun 20, 2001
I don't remember the chapter numbers off hand (and don't have a copy of the book handy) but I wrote the SAX chapter, the Socket I/O chapter, and the Server-Side Presentation chapters. I pretty much wrote them on my own with some guidance in that last chapter. The SAX chapter assumes no knowledge of SAX. It takes you through the entire API soup to nuts and describe each part in detail. It centers around JAXP which is becoming the de facto XML parsing framework. Another part of this chapter is that is shows you how to take a non-JAXP compliant parser and make it into one. For this I chose Aelfred. The Socket I/O chapter takes you through dealing with XML over a network. TCP/IP is explained in basic detail but design patterns are discussed that make reading XML over a network simpler. The Server-Side Presentation chapter talks about generating presentation markup using server-side technologies. I talk about Cocoon1 and give examples as to its use. This was the most exciting chapter for me because it deals with a very real problem: supporting display of one's content on many different browsers/devices. Coming from a background in the Wireless Internet this is a BIG problem: so many browsers (and more everyday) to support how can I do it with one codebase? I hope that you find the book informative and most of all helpful.
Originally posted by Stanley Tan: Jeremy Crosbie, With so many authors, were you assigned to write certain chapters or simply contribute to the overall progress? If you wrote separate chapters, what chapters did you write?
Sir Jeremy Crosbie, One of my favorite books is Debugging Java by Will David Mitchell. He says in his book that he had to quit his job to work on the book. Did you have a similar experience? Hopefully, one day, I'll be good enough to write my own book and I'm wondering if it's a really full-time job. How was your experience? By the way, where do I get the sample chapters for the book someone else was referring to?
Jeremy, I have read all the XML books published by Wrox and I can't stop wondering about the oversteppings. Consider XML Databases (by Kevin Williams), Professional Java XML and Professional XML. These three books have about 30% common content. What is the rationale in making the book FAT with redundant stuff? If you follow the career path at the back of the book, most of the times you end up reading the same stuff again and again in different books. This doesn't make sense even from the marketing standpoint. This is very typical of Wrox publications. If you look at others( O'Reilly, Sams, AW etc ), their books are very focussed and two books on the same subject has no or very minimal overstepping. I personally feel there is a lot of fat that can be removed from the "Professional Java XML" . Jeremy, do you have any insight into this very unique nature of Wrox publications?
------------------ Ajith Kallambella M. Sun Certified Programmer for the Java�2 Platform. IBM Certified Developer - XML and Related Technologies, V1.
Originally posted by Stanley Tan: Sir Jeremy Crosbie, One of my favorite books is Debugging Java by Will David Mitchell. He says in his book that he had to quit his job to work on the book. Did you have a similar experience?
Before Jeremy got chance to answer , I'll sneak in my guess that Wrox's marketing model with multiple authors was probably developed to prevent such drastic experience Another design goal apparently was to shorten book writing time. Technology changes so fast, so if one author had to write the whole book, it would be pretty outdated by the time it was published Yet another impication is that if authors do not have to quit their job, they are able to support themselves during writing process, thus lightening Wrox's financial burden