Hey
Richard Monson-Haefel wrote:
> Anyway, one thing that would help is remote references that were specified as
> being persistent. Then entity bean components could hold references to other
> entity beans as part of the persistent state. Obviously this would require
> non-OODB EJB containers to do more work, but it would provide a simpler model
> for the rest of us.
>
> Richard
> BTW - I know Ricard already has smart proxies but i'm talking about supporting
> it in the EJB specification ... I don't care how its manifested.
The best way to do this (IMHO) is to require the remote references to
implement javax.naming.Referenceable somehow. The only problem that I
can see is that as I understand it in a CORBA env. the client can
generate the stubs themselves which will make it impossible to get this
kind of code into the stubs. Workaround is to make the EJBObject have
some "public javax.naming.Reference getReference()" (i.e. instead of
getHandle) which does more or less the same thing only the method throws
RemoteException and the call requires a roundtrip to the server.
But I guess we'll see if something like this is included in EJB1.1,
which should be released Real Soon Now.
/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".
