What persistent information is a Jini service required to maintain?

The Jini specifications require that services maintain some state information across service crashes and restarts. This persistent state includes:

• The service ID. Once a service ID is acquired, that same service ID must be used each time the service registers with a lookup service. A service ID allows the service to be uniquely identified.
• The set of service attributes that were used when registering the service. Clients may look up services by matching attributes, so a service must ensure that it registers with the same set of attributes in all lookup services.
• The set of lookup groups the service has joined. The service should participate in the same groups when restarted.
• The set of lookup services in which the service should register using unicast discovery.