> -----Original Message-----
> From: Cedric Beust [mailto:[EMAIL PROTECTED]]
> Sent: Jueves, 23 de Agosto de 2001 16:34
> To: [EMAIL PROTECTED]
> Subject: Re: Decline of the EJB civilization?
>
>
> > From: A mailing list for Enterprise JavaBeans development
> > [mailto:[EMAIL PROTECTED]]On Behalf Of Winston Gnananayagam
>
> > Much had been hyped about the capability of the EJB container and
> > things it can do with Entity Beans. Today we see EB's as too
> > complicated/bloated to use or to maintain it and also is a
> major issue in
> > the applications performance.
>
> <snip>
>
> > Most of the applications today seem to use Session
> beans/Message
> > Driven Beans, to make some of their critical code to be
> distributable. Other
> > than that its plain old Servlet/JSP/JDBC. Look at those
> 100s of design
> > patterns dedicated to EJB's. Seems like we need a separate
> design pattern to
> > just use those 100s of patterns. I guess today, developers
> are saying
> > instead of implementing all those patterns, just make a
> freakin JDBC call
> > :-) To do just that , it doesn't make sense to pay all
> those money to buy a
> > costly application server.
> >
>
> Sweeping statements again... What are these "most of the
> applications"? Who is
> this "we"? Do they actually write applications with Entity
> beans or do they
> just dismiss them because they ran some benchmarks in a
> vacuum and were
> disappointed by the results?
I agree.
>
> Here are some facts:
>
> - Entity beans work. They were working okay with EJB 1.1,
> they work even better
> with 2.0. We have thousands of customers using them for
> high-volume Web sites
> and performance of Entity beans is almost never the issue
> (the issues are
> elsewhere, I can elaborate in a separate email)
I have proof of all of this; And can tell you most our problems' roots
are in a design with some holes on it (my fault entirely), mostly because
of inexperience. That's in the past for me now ;-). I have a homongous site
powered by EJB's. And yes, it is fast, scalable, resilient, etc.
>
> - Entity beans are not a panacea. You will find a lot of
> projects that do fine
> without them with simple Stateless session beans + JDBC. You
> can also find
> horror stories about Entity beans, like projects that
> started with them and
> then dropped them for a bunch of reasons. Regardless of the
> fact that it
> depends a lot on which application server they use, it's
> still not enough to
> deem them as totally inappropriate for mission-critical applications
>
> The only bad choice is an uninformed choice.
>
> If you have to pick a technology, make sure you know the ins
> and outs of all the
> candidates before you decide.
>
> > Btw, why is Sun coming up with parallel
> technologies to EJB like
> > JINI, JDO among others???
>
> That's a separate issue. You make it sound like there is a
> general strategy
> behind their actions, but for having worked there for a
> couple of years, I can
> tell you that just like all big corporations, there is no
> such concerted
> efforts. There are a lot of projects within Sun and a lot of the
> research-oriented ones come up with results on their own
> agenda. When this
> outcome is deemed interesting, Sun starts pushing it, even
> when it sometimes
> contradicts some of their previous releases.
>
> > Yeah maybe the EJB civilization is declining. But,
> > don't worry in few years we would be discussing this same
> topic about a
> > similar technology on a different forum.
>
> Most likely.
>
> --
> Cedric
>
> ==============================================================
> =============
> 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".
>
>
> ______________________________________________________________
> ______________
> For your protection, this e-mail message has been scanned for Viruses.
> Visit us at http://www.neoris.com/
>
===========================================================================
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".
