> speaking of JDO
> > - It also allows to design your business logic as a true OO
> system. I
>
> - You value purity of object orientation. This is not a
> judgement, just an
> observation.
Okay, that's true: if people don't need OO then the fact that
entity beans are not OO are not a reason contra entity beans.
> > - JDO offers a much better performance (this is not based
> on speculations
>
> - 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.
Yeah, entity beans with weblogic 4.51 perform really bad
(BEA doen't deny, they say you should use tools like toplink for WL)
Our architecture had a workaround to use a session bean
and plain sql when a lot of "rows" needed to be loaded from the database.
The workaround outperformed the entity beans by a considerable factor.
Another performance problem with EJB in WL 4.51 is that they do
remote calls when calling eachother, even if they are on the same server
===========================================================================
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".
