> Crude yes, but cruder than what? This first iteration of JDO will be
probably
> lack many of the features of products such as Cocobase or TopLink. I don't
use
> much CMP and if JDO proves to be robust enough, I may use it to persist my
> entity beans. I have a feeling that extensions to EJB 2.0 may allow me to
> overcome the two most lacking issues in BMP entity beans (IMHO):
>
> 1. Requirement of n+1 queries on Finders, and
> 2. Lack of PreparedStatement caching.
>

Oracle caches statements (prepared or called) in their latest JDBC driver.
You
could build your own statement caching mechanism into the JDBC driver of
your
choice if you need this feature for a different database.

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".

Reply via email to