## Uses of Class
java.util.prefs.BackingStoreException

- Packages that use BackingStoreException
  Package | Description
  --- | ---
  java.util.prefs | This package allows applications to store and retrieve user and system preference and configuration data.

- - ### Uses of BackingStoreException in java.util.prefs

    Methods in java.util.prefs that throw BackingStoreException
    Modifier and Type | Method and Description
    --- | ---
    `abstract String[]` | Preferences.`childrenNames()` Returns the names of the children of this preference node, relative to this node.
    `String[]` | AbstractPreferences.`childrenNames()` Implements the `children` method as per the specification in `Preferences.childrenNames()`.
    `protected abstract String[]` | AbstractPreferences.`childrenNamesSpi()` Returns the names of the children of this preference node.
    `abstract void` | Preferences.`clear()` Removes all of the preferences (key-value associations) in this preference node.
    `void` | AbstractPreferences.`clear()` Implements the `clear` method as per the specification in `Preferences.clear()`.
    `abstract void` | Preferences.`exportNode(OutputStream os)` Emits on the specified output stream an XML document representing all of the preferences contained in this node (but not its descendants).
    `void` | AbstractPreferences.`exportNode(OutputStream os)` Implements the `exportNode` method as per the specification in `Preferences.exportNode(OutputStream)`.
    `abstract void` | Preferences.`exportSubtree(OutputStream os)` Emits an XML document representing all of the preferences contained in this node and all of its descendants.
    `void` | AbstractPreferences.`exportSubtree(OutputStream os)` Implements the `exportSubtree` method as per the specification in `Preferences.exportSubtree(OutputStream)`.
    `abstract void` | Preferences.`flush()` Forces any changes in the contents of this preference node and its descendants to the persistent store.
    `void` | AbstractPreferences.`flush()` Implements the `flush` method as per the specification in `Preferences.flush()`.
    `protected abstract void` | AbstractPreferences.`flushSpi()` This method is invoked with this node locked.
    `protected AbstractPreferences` | AbstractPreferences.`getChild(String nodeName)` Returns the named child if it exists, or `null` if it does not.
    `abstract String[]` | Preferences.`keys()` Returns all of the keys that have an associated value in this preference node.
    `String[]` | AbstractPreferences.`keys()` Implements the `keys` method as per the specification in `Preferences.keys()`.
    `protected abstract String[]` | AbstractPreferences.`keysSpi()` Returns all of the keys that have an associated value in this preference node.
    `abstract boolean` | Preferences.`nodeExists(String pathName)` Returns true if the named preference node exists in the same tree as this node.
    `boolean` | AbstractPreferences.`nodeExists(String path)` Implements the `nodeExists` method as per the specification in `Preferences.nodeExists(String)`.
    `abstract void` | Preferences.`removeNode()` Removes this preference node and all of its descendants, invalidating any preferences contained in the removed nodes.
    `void` | AbstractPreferences.`removeNode()` Implements the `removeNode()` method as per the specification in `Preferences.removeNode()`.
    `protected abstract void` | AbstractPreferences.`removeNodeSpi()` Removes this preference node, invalidating it and any preferences that it contains.
    `abstract void` | Preferences.`sync()` Ensures that future reads from this preference node and its descendants reflect any changes that were committed to the persistent store (from any VM) prior to the `sync` invocation.
    `void` | AbstractPreferences.`sync()` Implements the `sync` method as per the specification in `Preferences.sync()`.
    `protected abstract void` | AbstractPreferences.`syncSpi()` This method is invoked with this node locked.

Submit a bug or feature
For further API reference and developer documentation, see Java SE Documentation. That documentation contains more detailed, developer-targeted descriptions, with conceptual overviews, definitions of terms, workarounds, and working code examples.
Copyright © 1993, 2015, Oracle and/or its affiliates. All rights reserved.