Richard Monson-Haefel wrote:
> An address would, IMO, be a
> poor example of an entity bean even if the data it represents could be shared.
Actually, I agree with you in this particular case. Sharing addresses
is usually accomplished through a separate shared object called
something like AddressEntry, that is jointly owned by many people and is
NOT destroyed until all parties who own it are destroyed. It is my
contention that that SHOULD be a bean, although PostalAddress is
currently modelled in our system as a Serializable object.
> In addition, there are transaction deadlocks to consider. Shared data means
> isolated data under certain circumstances. The more shared data you have the
> more instances of deadlocks you will encounter. Its a simple but possibly
> explosive problem.
Yes; although in most cases the business requirements pretty much
mandate it. :-(
Cheers,
Laird
===========================================================================
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".
