Mark Brouwer wrote:
For some APIs in com.sun.jini there might be value in a compatibility layer such as the starter framework among other things people often refer to in configuration files. For most of the classes though in com.sun.* I don't think there is much reliance on (these are merely the implementation details for the net.jini API or represent the contributed services).
Here's a quick take at where various com.sun.jini classes might likely be referenced: .admin.DestroyAdmin - admin proxy classes, admin proxy users .config.<multiple> - config files .discovery.<multiple> - constraints in config files .landlord.<multiple> - lease implementations .lease.<multiple> - lease implementations .logging.Levels - logging property files .lookup.entry.BasicServiceType - service impls .mahalo.<multiple>Impl - config files .mahalo.MahaloPermission - security policy files .mercurity.<multiple>Impl - config files .mercury.MercuryPermission - security policy files .norm.<multiple>Impl - config files .norm.NormPermission - security policy files .outrigger.<multiple>Impl - config files .outrigger.JavaSpaceAdmin/AdminIterator - admin proxy users (deprecated) .outrigger.OutriggerPermission - security policy files .phoenix.<multiple> - config files .reggie.<multiple>Impl - config files .reggie.RegistrarPermission - security policy files .start.LifeCycle/ServiceProxyAccessor - service impl classes .start.<multiple> - config files .thread.TaskManager - config files .tool.<multiple> - ant tasks, config files - Bob
