> WL 4.5.1 is sort of old news. Yes, old versions s*uck, but
> let's move on to
> the current stuff at least. The app servers I am using all
> short circuit
> the remote call logic if beans are resident in the same JVM.
Ok, happy to hear that's been fixed.
Another major concern regarding performance is finder methods.
If you need to load say thousands of entity beans from the database,
how does the spec say the container should do it: row per row or all rows
at once? If it loads them row by row then entity beans are no good
in scenarios where you often need to load lots of entity beans.
> As for OO, let's not debate the purity of entity beans;
> anybody using an
> RDBMS has sacrificed their object purity for a scalable
> robust solution.
> Put me first on the list.
I agree that EJB is a relational model.
I am willing to sacrifice inheritance in EJB. But I still need
decent support for aggregation and as long as that doesn't
happen I think entity beans are no good. So why doesn't
the EJB 2.0 get into its final phase?
===========================================================================
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".
