Glenn wrote:
>
>Similar queries can be used to access relational databases from
>either many fine grained deployed components (entity beans) or from the
>same number of fine grained objects embedded in a single entity bean.
>(Assuming that bean managed persistance is used for either case.)
Oh, assuming BMP. I was thinking from the perspective of CMP, that is,
maximum automation. I'm concerned with discovering the patterns of EJB
development and (re-)deployment which require the *least* amount of human
intervention. BMP should only be used as a last resort when CMP is
either a performance or mapping obstacle.
>>>Coarse grained object graphs allow us more control over how we query our
>>>RDBMS.
>>
>>Please explain.
>
>It may be more efficient to obtain many rows of many related tables using
>a single query or view and build an object graph from the results of
>this query.
But we weren't talking about runtime performance, were we? You said
"control over how we query" which implies design time, not run time.
So I'll reword my claim:
Smaller entities are easier to map AT DESIGN TIME.
===========================================================================
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".
