Lines Matching refs:of
9 * with the License. You may obtain a copy of the License at
39 /** manages one, or more, complete sets of configuration data for
41 provide access to subsets of these shared configurations.
43 <p>Shared sets of configuration data usually serve to provide defaults,
45 store multiple layers of defaults may be combined with a user-specific layer
48 <p>Many aspects of the supported behavior depend strongly on the underlying
53 <p>On the other hand, in the simplest model there is only a single layer of
59 select the configuration data source. They may also define the scope of
70 layer of configuration data of the current user context. It should in
79 of the configuration.
88 <p>Using the first of these service specifiers requests a read-only view of
91 To reflect its <em>element role</em> as root of the view, it implements
95 <p>Using the second form requests an updatable view of the configuration.
100 <BR />If the root element of the view is marked read-only (as indicated
110 changes will apply. They also specify the view of that configuration that
111 should be created. That is, they determine the subset of elements that can be
112 accessed starting from the returned object. Each element of the argument
118 <p>What combinations of arguments are supported depends on the service name
122 <p>With both of the standard service-specifiers above, an implementation must
123 accept a single argument named <code>nodepath</code> of type <atom>string</atom>.
124 This argument must contain the absolute path to an element of the
125 configuration. The view that is selected consists of the named element and
133 the behavior of the view. These are different for different implementations
148 This also allows targetted setting of values for selected locales.
158 had been called using an empty sequence of arguments.
164 /** allows controlling or observing the lifetime of the configuration.
166 <p>The owner of the provider may dispose of this object
171 the provider. Therefore, disposing of the provider will cause all objects
172 belonging to these views to be disposed of as well. This does not apply to
173 <em>snapshot</em> views that have their own copy of the data, if available.