Hey
Andrzej Jan Taramina wrote:
> > Sideeffect: beans can implement Account, thus ensuring consistency
> > between interface and impl.
>
> You can do this now (though some EJB Server deployment tools use
> getDeclaredMethods() and have some problems handling it properly).
> Just put all your business methods in a different interface:
>
> // Written by bean developer
> interface AccountBiz
> {
> long getBalance();
> ...
> }
But with the model I suggested the developer only have to make one
interface which can be used directly. This requires two (although the
second is generatable).
> > Comments? This is an incompatible change to the existing interfaces, but
> > it has some very nice effects IMHO, including making it possible to
> > implement EJB over plain JDK-RMI(/w JRMP).
>
> I think it is impractical for just the reason that it is a serious
> incompatibility with the current spec. I don't think you will see the
> requirement for EJBObject to extend Remote being dropped any time
> in the near term.
Me neither.. too bad it wasn't like that in the first place. It would
have worked just as now, only with more implementation options.
> However, since java.rmi.Remote is just a marker interface (with no
> method signatures), having it in the inheritance chain for the interface
> should not prevent you from doing the things you want. What might be
> better is to change EJBObject so that it also implements Serializable
> and thus allows you to pass around the stubs at will over the wire.
I don't get this. The stubs *are* being sent over the wire and there's
nothing one can do about it. Having EJBObject implement Serializable
won't help at all. Could you expand on this?
/Rickard
--
Rickard �berg
Computer Science student@LiTH
@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".
