Ah, so the real question is, "Why should you use entity beans?"
You have given us a few data points.
speaking of JDO
> - 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.
- You value purity of object orientation. This is not a judgement, just an
observation.
> 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?
- You don't need entity beans.
> - 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?
- You have some prior experience with entity beans in which they have
performance X, and you speculate that JDO will be nX where n > 1.
> Ha, finally, the opportunity to give my anti entity beans speach :)
- You go around giving anti-entity bean speeches.
I personally think JDO is a perfect fit for you. Go for it!
Cheers
Jay Walters
===========================================================================
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".
