|
The Preferences API allows applications to store and retrieve configuration data in an implementation-dependent backing store. Asynchronous updates are supported, and the same set of preferences can be safely updated by multiple threads and even multiple applications. For more information, refer to the Preferences API Guide.
An application deployed in a JAR archive uses a manifest to describe the contents of the archive. For more information, refer to the Packaging Programs in JAR Files lesson.
The configuration of a Java Web Start application is contained in a JNLP file. For more information, refer to the Java Web Start lesson.
The configuration of a Java Plug-in applet is partially
determined by the HTML tags used to embed the applet in the web page.
Depending on the applet and the browser, these tags can include
<applet>, <object>,
<embed>, and <param>. For more
information, refer to the
Java Applets
lesson.
The class
java.util.ServiceLoader
provides a simple service provider facility. A service
provider is an implementation of a service — a well-known set
of interfaces and (usually abstract) classes. The classes in a service
provider typically implement the interfaces and
subclass the classes defined in the service. Service providers
can be installed as extensions (see
The Extension Mechanism).
Providers can also be made available by adding
them to the class path or by some other
platform-specific means.
|
