Rickard,
>But since the server is the *only* local referrer you know that if DGC
>tells you it's unreferenced, you can reclaim it. All clients must (?)
>use remote references for talking to it.
What about peer (i.e. local) bean instances? The entity objects are remote
already. Do you mean all (including local) clients should talk to the
objects through the stubs? Stubs for a remote object are shared locally.
Also there seems to be a strong reference to the stub itself in the standard
jdk1.1 stub-table.
>How will this relate to the upcoming EJB spec. release where RMI/IIOP
>will be mandated (since RMI/IIOP doesn't support DGC!!!!)??
Mandated? The following (EJB 1.1 spec, page 39):
"The use of the EJB to CORBA mapping by the EJB Server is not a requirement
for EJB 1.1 compliance. A later release of the J2EE platform is likely to
require the [sic] that the J2EE platform vendor implement the EJB to CORBA
mapping."
only tells me that the mapping has to be implemented and available at one
point. It does not say that the mapping has to be used exclusively (i.e. at
all times and with all clients).
Regardless of my reading of the spec, what you raised is still an issue.
Anyone care to comment?
Imre Kifor
Valto Systems
===========================================================================
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".
