setUp

Note: If this is a service restart then Configuration is NOT
overwritten. If you want to change the Configuration of a
service which has already been started you need to either administer
it through jini or shut it down and edit its configuration file.

writeEntries

writeEntry

Write out the ctor for an Entry. For example, generating
new net.jini.lookup.entry.Name("foo") when given a
Name.

Note: There is no general purpose mechanism for emitting
Entry attributes using reflection, even when the
Entry is an AbstractEntry (ctors do not declare the
relationship between their arguments and the public fields). Further,
jini will not let you use the zero arg public ctor and then set the
fields from the public fields declared by the Entry class from within
the generated configuration file. For example,
_entry1.name = "foo"; is rejected by the
ConfigurationProvider. This unpleasant situation means that
we are hardcoding the ctor calls based on the class. However, you can
use this method as a hook to extend the logic to handle Entry
implementations which it does not already understand.

writeExporterEntry

Writes the
AbstractServer.ConfigurationOptions#SERVICE_ID_FILE entry.
This value is used by the AbstractServer to export the proxy
for the service. The choice here effects the protocol that will be
used for communications between the clients and the service.
FIXME the [exporter] is hardwired. There are also hardwired exporters
used by the JiniFederation. The whole issue needs to be
resolved. The exported is a chunk of code, so it would have to be
quoted to get passed along, which is why I am doing it this way.

awaitServiceDiscoveryOrDeath

Waits up to timeout units for the service to either by discovered by
jini or to die.

Note: We recognize the service by the present of the assigned
ServiceToken attribute. If a service with that
ServiceToken can not be discovered by jini after a timeout,
then we presume that the service could not start and throw an
exception. The ServiceToken provides an attribute which is
assigned by the service starter while the ServiceID is
assigned by jini only after the service has joined with a jini
registrar.