Re: More odd behaviour

Rawlings, Bill A wrote:
> Thanks for the responses guys.  I figured it was a lease waiting to=20
> expire.  I guess I can get around it by setting the LUS status to be=20
> =93down=94 right after the destroy() call, because that does indeed kil=
l the=20
> LUS.
>=20
> I=92d like to use this problem as something I think is important for=20
> future River use.  This is an app I should not have to be writing.

The com.sun.jini.start.ServerStarter class illustrates how a container ca=
n be=20
created which uses the ApplicationDescriptor mechanisms to manage service=
=20
instance lifecycle.  It is configuration based in that application, but c=
ould be=20
done with a GUI as well.  I started to do something along these lines a w=
hile=20
back, but put it aside when some other work intervened.

What little I got done is out at: http://pescade.dev.java.net/

Gregg Wonderly

-------------------------------------------------------------------------=
-
Getting Started:     http://www.jini.org/wiki/Category:Getting_Started
Community Web Site:  http://jini.org
jini-users Archive:  http://archives.java.sun.com/archives/jini-users.htm=
l
Unsubscribing:       email "signoff JINI-USERS"  to [email protected]