> Anyway, I
> guess the best way would to provide an interface that both the remote
> interface and bean class would implement.
That's right.
There is one often overlooked issue with this approach though.
The business methods in the remote interface must all throw
RemoteException per EJB spec, but the implementation doesn't have to.
Except when you use this pattern, now the impl implements the business
interface and must all of a sudden also throw the RemoteException
and it cannot throw exceptions not specified in the business interface.
Frank
-----Original Message-----
From: A mailing list for Enterprise JavaBeans development
[mailto:[EMAIL PROTECTED]]On Behalf Of Andy L. Czerwonka
Sent: Tuesday, November 16, 1999 11:33 PM
To: [EMAIL PROTECTED]
Subject: Re: Remote Interface Question
Andy,
Also beware that while the EJB spec permits a bean class to implement its
remote interface, not all EJB implementations support it (WebLogic doesn't).
Stu Halloway
DevelopMentor
[ALC] I don't quite understand why it wouldn't be supported. Anyway, I
guess the best way would to provide an interface that both the remote
interface and bean class would implement.
_____________________
Andy L. Czerwonka
CORBATECH Inc.
(403) 547-8892
===========================================================================
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".
===========================================================================
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".
