Hi
Can someone in the know clarify the issue of when clients are expected
to make and terminate connections to the server ?
Is this supposed to be part of the spec ? If so, the following questions
apply, if not, please clarify the owner of this issue as part of the spec.
Is there a way to force a client to maintain a virtual connection (i.e. hold
bean stubs) but drop the socket connection ? IHAC who wants to
support a degree of off-line working, but can't disconnect from the
server as it (Tengah3.2) seems to hold the connection open forever.
My assumption at the moment is that a connection is opened with the
first retrieval of a "Home" interface, and closed with the GC of the
last active instance of a Home, Session or Entity bean in the
client. This doesn't seem to work in Tengah or ND.
If this is the case I think that more control is needed to manage
the underlying transport layers in order to 1) manage errors by permitting
a client to perform a hard disconnect irrespective of the handles it has
open 2) permit off-line disconnection/re-connection of the transport layers
without affecting the EJB handles.
Thanks for any clarification
Joel Crisp, Senior Java Architect, SUN Microsystems
===========================================================================
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".
