<snip/>
HI,
I think either you or I have to reread the spec ;-). The abstract methods
for setting a cmp-field are part of the contract between the bean provider
and the persistence manager and NOT the client. if you don't want to expose
the setter for a CMP field then simply don't. if it's not part of the
remote interface it will not be accessible to clients. Remember, they don't
have access to the bean impl, just the remote interface.
I don't see the problem or am I missing something?
regards,
robert
>Now I have _no_ guarantee that nobody will accidently call the original
>setBalance() method, thereby circumventing my little security system, which
>was supposed to check for a negative balance. But, hey, I thought, then I
>will just declare the original setBalance() as protected - unfortunately
>that is not allowed by the specification.
>
>I would r e a l l y like to hear from anybody who knows a solution to this.
>Any comments would be most welcomed.
>
>Randahl
>
(-) Robert Krüger
(-) SIGNAL 7 Gesellschaft für Informationstechnologie mbH
(-) Brüder-Knauß-Str. 79 - 64285 Darmstadt,
(-) Tel: 06151 665401, Fax: 06151 665373
(-) [EMAIL PROTECTED], www.signal7.de
