Winston Gnananayagam wrote:
> I think this discussion is going more towards whether developing
> applications on Open source products is better than Commercial vendors or
> not . Well, this has been an age old debate since MS Vs. Linux. Probably not
> a discussion for this forum.
It a side issue to the article in question.
>
> Well, to think about the core issue of the suggested article, yeah I
> would agree that EJB has been hyped a lot without delivering much on its
> promises. Managers, Architects, Developers, all of them seem to have fallen
> into those sales pitches(including me). If Managers made the mistake of
> buying those costly products not knowing its capabilities, then developers
> have fallen into the trap of making design decisions on something that just
> does not work or has been a nightmare just to maintain it(E.g.. Entity
> Beans). 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. I'm not saying that EJB is a useless
> technology, but just that its capabilities have been hyped a lot. EJB's need
> to be used cautiously, its not a one solution fits all(as its hyped, to milk
> money out of corporations).
EJB has been hyped, but I disagree that is doesn't deliver on its promises.
Entity beans have been extremely useful in our application. The biggest mistakes
made by manangers and developers was to believe the hype that the vendor's
product was all you needed to realize the full EJB promise. For the first two
versions of the spec, you couldn't develop applications with complex domain
models without a third party O-R mapping tool or a good Object database. The
only exception might be Gemstone, but I haven't used their product.
Of course, hype is what this industry is about. You can expect everyone else to
stand by and watch Microsoft do all the milking ;-)
>
> 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.
Of course there are/were plenty of expensive app servers which only support
Servlet/JSP/JDBC. The only inexpensive ones I know of are open source.
>
> Btw, why is Sun coming up with parallel technologies to EJB like
> JINI, JDO among others???
JINI is a non transactional distributed architecture and JDO is a non
distributed data model. They only seem parallel if you don't look very closely.
--Victor
===========================================================================
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".
