Hey
James Cook wrote:
> I'm sorry, I got the spec wrong. It is 6.10.5.
Ah, ok. That makes much more sense ;-)
But it's in the details. I assume you're referring to this piece:
"For each method defined in the remote interface, there must be a
matching method in the ses-sion
bean�s class. The matching method must have:
� The same name.
� The same number and types of arguments, and the same return type.
� All the exceptions defined in the throws clause of the matching method
of the session
bean class must be defined in the throws clause of the method of the
remote interface."
Which only says that any exceptions defined in the bean must be in the
interface, but not the other way round...
> After re-reading my original post, I thought someone would call me on my
> mistake. The bean does not *have* to throw RemoteException. The remote
> interface methods, however, *do* have to. This causes a client, that uses an
> object that implements this interface, to catch RemoteExceptions. Even local
> objects.
Well, I had already noted this in my reply to Frank, so I didn't think
it would be necessary to say it again.
/Rickard
--
Rickard �berg
@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".
