> It's ironic that this comes up. Today I pre-ordered the book from Amazon (it
> isn't shipping yet), but I also wrote my own review. I don't know if Amazon
> will let it get posted however.
It's already posted.
> My peeve, is that every review of Tom's yet to be release book is
> (hopefully) from associates that Tom (or the publisher) has doled the book
> out to before it is officially released. The book *may* actually be as good
> as they say, but they all (several people) unanimously proclaim it the best
> book they've ever read. This does me absolutely no good at all in deciding
> if I should buy it. I wish Tom (or the publisher) would of posted some of
> the more negative reviews, if they exist.
I _do_ know that all the reviewers thus far (except you) have read the book.
The people listed in the "reviews" section participated in the technical
edit of the manuscript. The people in the "customer comments" section
wrote the review themselves. (Mala Chandra also wrote the foreword to
the book. Jerry Cosimar wrote me an email and asked if he could get an
early look at the manuscript; I was happy to oblige.).
> Of course my gripe is mute (and apologies in order), if in fact Tom posted
> all of the candid reviews of his book and they were all 5 stars. Regardless,
> it promises to be one of the first books out, and therefore a must buy. I
> promise to post my own review of the book once I read it.
I didn't post any of the reviews. The publisher posted the ones in the
"reviews" section; the ones in the "customer comments" section were posted
by the people who wrote them.
I'm not complaining, by the way. :-)
> BTW Tom, will the book contain a last minute chapter on the Moscone spec and
> some technical discussion of how it will affect us developers?
The "last minute" happened a couple of month ago. The book is printed,
bound, and being shipped. (Yes, I've held the finished product in my hand).
I'm putting together an online supplement for the book; I probably won't
put it up until after the spec is finalized next month. (When I first
started this project, I was very concerned because I _knew_ that there
would be quite a few spec revisions over the next few years. I decided
that the best approach to the problem was to put up a companion website
for the book and post supplemental information there. (Similar to what
Doug Lea did with his book on Concurrent Programming in Java). When
I finalize the supplement, it'll be available from:
http://cseng.aw.com/bookdetail.qry?ISBN=0-201-60446-9&ptype=0
In general, I don't think that the Moscone release will impact developers
_too_ heavily. I've only skimmed it at this point, but the only surprise
I saw was the fact that entity EJBs will be mandatory for 1.1 instead
of 2.0, as originally promised). Most of the spec changes are to tighten
up formerly vague areas in the spec. The other big change is the XML-based
deployment descriptors. Presumably, development environments will be
backward-compatible, so that you can continue to use whatever DDs you've
built to date. I'd expect that most vendors will come out with translators
that will translate their old DD formats to the new XML format. Most
EJB container vendors have _some_ sort of GUI DD-builder tool that obviates
the need for developers to muck about with DDs anyway.
Summary: Moscone's impact will be mainly on component providers.
Caveat: As I said, I've only skimmed it at this point. I've got a lot
of reading and rereading to do over the next few weeks.
===========================================================================
Tom Valesky -- [EMAIL PROTECTED]
http://www.patriot.net/users/tvalesky
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
