Hi,
On Fri, 19 Jan 2001, Steve Stearns wrote:
> Ahhhhh... Okay, so Category is a valid RMI object (since it's a
> descendant of Remote), but Remote isn't serializable. Therefore it
> won't work with IIOP and so it violates EJB 1.1. Got it :). I thought
> that since it was a descendant of Remote it would be okay to do that but
> I guess not.
Actually subinterfaces of Remote are legal IIOP remote interfaces as well.
The requirement for serialization is correct, but this is not why the
verifier is complaining (serialization is a run-time requirement, not
compile time).
But to be a legal IIOP remote interface all your methods in the remote
interface must declare java.rmi.RemoteException in their throws clause. So
check the methods in the Category interface and add the missing throws to
all methods there. This requirement is not just for IIOP compliance,
it's a requirement for all EJB remote interfaces. So you should have
received a whole bunch of other warnings as well.
-- Juha
--
--------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
List Help?: [EMAIL PROTECTED]
