I completely understand where you're trying to go. However, keep in mind
Entity beans are not meant to hold business rules. They are an interface
to
your physical storage.
We have solved that problem using a facade pattern that basically works
by
shielding the developper from the actual
Hi Randahl,
Why don't you just leave the method setBalance(float b)
out of the remote interface and put
public void setBalanceAndDoWhatHasToBeDoneWhenYouSetBalance(Float balance)
in the remote interface. So no other objects can call setBalance but only
Yep, as I wrote in an earlier post, that was what I chose to do.
Randahl
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of wim veninga
Sent: 22. februar 2001 15:38
To: Orion-Interest
Subject: Re: No influence on CMP 2.0 getter setter methods - a feature
I have been reading the CMP 2.0 specification and I think it is simply
great! Still, I am a bit surprised that the bean developer has no control
over what happens when a field is set. Imagine an AccountBean, for instance:
public abstract class AccountBean extends EntityBean {
Title: RE: No influence on CMP 2.0 getter setter methods - a feature or a bug?
This is why the session-bean-wrapping-entity-bean pattern
is so popular. Do not implement business logic inside your
entity bean. Instead, have your client perform operations
to the data via a session bean.
