Hi!
[EMAIL PROTECTED] wrote:
> I have read back and forth about DON'T reference entity beans from another
> entity beans, as well as the opposite. I have failed to get a good logical
> reason why this is bad and obviously is entities referencing each other
> convenient from time to time.
Where have you read that one shouldn't reference other EntityBeans? On
the contrary, referencing EntityBeans in an Entity is a very important
design and implementation tool.
> For example: I want to use CMP beacause it's fast to develop and the
> database is very simple. A person has a bunch of phone numbers. If I design
> the person entity bean to have a bunch phone number entities in a vector.
> (The vector IS NOT a CM field). Otherwise I need a session bean (or the
> client, god forbid) to be a proxy for these two entity beans to have some
> useful object to work with.
> Of two bad things, I think the first one is the best.
I don't think I would model Phone nrs as an EntityBean. But if you want
to, I don't see any problems with referencing it from your Person
entity.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.dreambean.com
Question reality
===========================================================================
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".
