Just a little note...
John O'Shea wrote:
> How handles are implemented is a container implementation issue. A
> decent container implementation can create EJB Handles which are
> independent of the container process, port number and host name. A more
> restrictive container implementation would encode location specific info
> directly into the handle and therefore constrain that container's EJBs
> to execution in that location only.
> Ideally, containers should be able to transparently shut down and
> relocate to a different server (and host if necessary) without
> invalidating already-exported EJBHandles. This is most useful for
> Entity bean handles and all types of Home handles.
On references in general.
There are (at least) 3 ways to do bean referencing:
* Use the primary key
* Use Handles
* Use CMP, do nothing, and let the container figure out how to maintain
references
If possible, I prefer the last one, as it requires the least amount of
coding. Clean and simple. Most OODBS-based containers should be able to
do this (I believe Gemstone handles this to perfection).
/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".
