Hi all, I'm currently looking at patterns for use in modelling entity beans.
I have heard/read that Entity beans should represent course grained obejcts.
However, lets say I have a Entity Bean called Customer. I now decide that I
have differing customer classes such as PremiumCustomer and
NonPremiumCustomer where the behaviour of the customer is determined by its
subclass.
As I understand it, inheritance is not allowed in Entity beans or at the
very least one should be extremely careful using it? I am now considering
modelling this using Role modelling/typing patterns? ie encapsulate the
behavioural differences against the role/type or at least use role/type to
overload Entity bean methods?
Or am I incorrect and Inheritance can be applied (carefully) to Entity
beans?
Are there any guidelines available yet on these sort of issues for
relatively new EJB players such as myself? Does Tom's book address these
sorts of "architectural/design pattern" issues.
Any comment/ideas greatly appreciated.
Rob Masters
Sun Certified Java Programmer
Comcare Australia
(w) 02 6275 0632
(f) 02 657 4045
[EMAIL PROTECTED]
http://www.comcare.gov.au
===========================================================================
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".
