The lookup service finds a match and notifies the exported remote event
listener. The event is unmarshalled with a context class loader of B and
a default class loader of B, this will result in the creation of a class
loader D that has B as its parent. The service item part of the event is
usable in the context of the plugin but in this case the SDM rejects the
event because it turns out the source of the registration and the field
doesn't match. Analysis learns that the source of the registration is
I must be missing something here, but do you see any exception from the
SDM, or is the event silently dropped? In the case of reggie, its proxy
implements equals (which the SDM uses to check for equality) to do a
comparison on the net.jini.id.Uuid value returned from getReferentUuid.
Is it that your registrar proxy does not do the same? Given the
specification of ReferentUuid, it's probably better to actually compare
the Uuids rather than test for equals - I can't answer the
history/rationale behind the current state of the implementation.
--
- vinod
