Hi Jun,
Thank you for your contribution,
I agree that the ejbRemove() method must only invoked once in the life
cycle of
a session bean's instance, when it pass to the method-ready pool state
to the
does not exist state.
Implementing java.rmi.server.Unreferenced interface is interesting to be
notified
when there are no more client that refence the session bean.
The only problem that I see for the moment is that only RMI/JRMP
implements
Distributed Garbage collector, Jeremie doesn't in the current version.
But France Telecom people that have implemented Jeremie has told me that
somebody's
working on a dgc for Jeremie.
As you know, we are currently working on JOnAS to implement instances
pools for
stateless and entity beans so I cannot garanty you that we will take
your modifications
as it, but we will study it carefully.
Thanks again
Best regards,
--
Philippe
Philippe Coq Evidian Phone: (33) 04 76 29 78 49
Bull S.A - 1 rue de Provence - 38432 Echirolles Cedex France
Download our EJBServer at http://www.objectweb.org
----
This list is cross-posted to two mail lists. To unsubscribe,
follow the instructions below for the list you subscribed to.
For objectweb.org: send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe ejb-container-group".
For enhydra.org: send email to [EMAIL PROTECTED] and include
in the body of the message "unsubscribe ejb-container-group".
