I am beginning to design EJBs, and have come across an issue with how to
design them. For example, we have many different type of addresses (Client,
Contact, Company, etc), and so I have created an Address bean that gets and
sets the Address no matter what type it is passed. When I get to the
Client, though, I am thinking about creating a Client bean, that has methods
to get and set the name, status, etc. However, using the same model as I
did with the Address, it makes more sense to create a Name bean, to get and
set Names (Client, Contact, Company, etc). I see benefits to both sides.
The Name bean gives me much greater re-use of code, but seems to be too low
a level of granularity. However, if I place it at the Client level, then I
am duplicating code left and right. I could have the methods in the Client
call a Name bean, but that seems to be too much overhead. Would someone
provide suggestions on how they handle this, or point me to a resource on
the Web?
Thanks,
Chip Whiteside
===========================================================================
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".
