<soapbox>
At first I was infuriated while reading Sessions' article, but after
following this thread and thinking about it some more, I realized that this
article does reflect on a side of reality that we as EJB developers don't
see every day.
Like many developers out there, Sessions just didn't get it. That would
include many Java programmers too, by my observations and unscientific poll
of attendees at JavaOne.
Sessions represent the group of seasoned developers (OK, I'm giving him
the benefit of the doubt, and I'm being very generous) who had crafted
robust, scalable applications without the use of EJB or Java. Given the
lack of access to EJB we have today, the due diligence required to separate
fact from fiction, how can you fault anyone who's on the outside trying to
figure this out? IMHO the article does point out some of the confusing
issues a novice EJB programmer would find.
</soapbox>
-Eugene
===========================================================================
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".
