Hey
Ed Roman wrote:
> What do you mean when you say you are using entity beans to describe your
> core business logic? You should only be using entity beans for minimal
> data-related logic, such as data decompression, get/set methods, etc. Keep
> all your business process logic in session beans. That is really your
> design pattern: write a session bean that handles your business logic, and
> have it use an entity bean to represent its data.
Why should it only be minimalistic? IMHO EntityBeans should have all
logic that is relevant for it to have. I don't see any reason to divide
this so that SessionBeans hold logic that could just as well be put in
EntityBeans. E.g. in SessionBean:
public void withdraw(Account acct, int amount)
instead of in EntityBean:
public void withdraw(int amount)
Why do you want to be restricitive about putting logic into EntityBeans?
That seems like the whole point, or you could just as easily use
SessionBeans /w JDBC calls directly...
/Rickard
--
Rickard �berg
Computer Science student@LiTH
@home: +46 13 177937
Email: [EMAIL PROTECTED]
Homepage: http://www-und.ida.liu.se/~ricob684
===========================================================================
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".
