At 17:39 10/5/00 -0700, Nathan Meyers wrote:
>On Thu, Oct 05, 2000 at 11:59:21PM +0000, Mark Ogden wrote:
> > Here's a quick question...Sorry to waste people's time but what are the
> > essential differences between JavaBeans and EJB from a practical point of
> > view?
>They aren't similar in the least, except in name. JavaBeans is a
>general-purpose component architecture, EJB is a spec for components
>that reside in a particular setting (an EJB container) and is neither a
>subset or superset of JavaBeans.
To take it a step farther, JavaBeans tend to be client side and View
oriented (view as in model/view/controller, not necessarily GUI). EJBs
are intended to be server side and are more Model (Entity) and Controller
(Session) oriented. JavaBeans also are very much Object Oriented, if
you're comfortable with OOA/D then you'll grok the JavaBeans programming
model. EJBs on the other hand tend to be very heavily procedural (Session)
and relational (Entity). When you compare the EJB model to a real object
oriented component model such as IBM SanFrancisco you discover that EJBs
were intended to "wrapper old stuff"* like relational databases, stored
procedures and RPG. Unfortunately what the SanFrancisco people learned is
that most development groups today won't expend the needed effort to really
learn the model; but those that do achieved amazing productivity and code
reuse. Combine that with a failure to leverage Linux and OS/2 (yes, I said
OS/2) and a truly backwards revenue model and it's no longer a surprises
that none of you know what SanFrancisco is/was, but everyone recognizes
EJB.
*The person I'm quoting actually has a different ending of that statement. ;}
----------------------------------------------------------------------
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
