Marcus Ahnve wrote:
> I guess it does not totally solve the issue of being totally OO with entity beans,
> but it is a good start.
Yes. The thing that gets in the way (that ALWAYS gets in the way) is
the fact that pretty much everything in the world has to throw
RemoteExceptions. One way to get around that if you trust your fellow
developers to catch when necessary is to declare everything to throw
RemoteException, all the way up the stack, whether you have any idea
whether the object that is doing the throwing will in fact be used as a
remote object. That is, factor RemoteException out of your design
entirely by declaring everything to throw it (since, IMHO, it probably
should have been a RuntimeException anyhow).
So for example at design time where you aren't concerned about
distribution and remote-vs.-local issues, you might come up with the
need for a Person object. Without even thinking about it, make sure
that all of Person's methods throw RemoteException, even if Person
itself will not implement Remote.
(Controversial advice, I know. :-))
Cheers,
Laird
===========================================================================
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".
