-----Original Message-----
From: John Yu <[EMAIL PROTECTED]>
>Question 2
>----------
>Since each call to an bean is a remote call (ignore co-located clients
>for the sake of this discussion), we should not model our business
>objects by too fine grain entity beans and methods if performance is a
>concern. But, doesn't that mean the EJB architecture imposes artifical
>constraints onto your Implementation Object Model
You should continue to model using fine-grained objects if that's what your
Object Model requires. The potential performance problem is solved in the
EJB world by using a Session Bean to encapsulate the transactions which
involve these fine-grained Entity Beans. Most of the action then takes
place on the server. The client should generally only see an Entity Bean
where the client is only concerned with that one Bean, e.g. where there is a
screen for editing that Entity Bean's properties. That's the theory anyway.
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
