Ha, finally, the opportunity to give my anti entity beans speach :)
> I think Entity beans are a good mechanism to represent a
> persistent business
> object. Many of the "problems" that developers have with
> entity beans center
> around things like concurrency control and the complexity of coding
> course-grained beans. Unless you are using an EJB 2.0 (maybe
> it won't be until
> 3.0 until this is actually made easier) implementation or
> some complicated
> framework (TopLink), this will always be a complicated task.
Sounds nice but I am sceptical... (see below)
> Perhaps you have looked at JDO and can enlighten me. What
> will JDO get you that
> CMP doesn't already offer?
- JDO offers a much better performance (this is not based on speculations
but on experiences. I don't have experience with JDO I must admit, but I do
have experience with entity beans) because entity beans are distributed. Why
would you want entity beans to be distributed if they are wrapped by session
beans?
- It also allows to design your business logic as a true OO system. I think
EJB 1.1 is much closer to the relational model than to the OO model. And if
you look at how the EJB 2.0 doesn't get finalized as they try to move closer
to being an OO model.
> I view JDO as a declarative
> persistence framework.
> The same challenges face the developer that uses JDO as the
> developer that uses
> Entity Beans.
Okay, that's true. But given the two disadvantages of entity beans, I still
don't consider this as a reason to use entity beans.
> JDO seems like a good alternative for
> persisting objects *outside*
> of the EJB framework, but if you know you will be using EJBs,
> why bother?
Well, my architecture will be such that plain java classes represent the
business logic and that they are made persistent using I don't know yet
which technology. It could be entity beans, but in that case the entity
beans will not contain any business logic. They will just do persistence.
But I first need a good reason to use entity beans...
I only need EJB for distribution, transaction management, authentication and
autorization, but that's something of which session beans take care. So my
question remains: why would I want to use entity beans?
geert
===========================================================================
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".
