Lines Matching refs:p
43 <p>Shared sets of configuration data usually serve to provide defaults,
47 </p>
48 <p>Many aspects of the supported behavior depend strongly on the underlying
52 </p>
53 <p>On the other hand, in the simplest model there is only a single layer of
55 </p>
56 <p>An implementation is usually obtained from a
63 </p>
69 <p>A <type> ConfigurationProvider</type> provides access to the personal
74 </p>
81 <p>The parameter <var>aServiceSpecifier</var> passed to
86 </p>
88 <p>Using the first of these service specifiers requests a read-only view of
93 </p>
95 <p>Using the second form requests an updatable view of the configuration.
104 </p>
106 <p>The arguments passed to
116 </p>
118 <p>What combinations of arguments are supported depends on the service name
120 </p>
122 <p>With both of the standard service-specifiers above, an implementation must
130 </p>
132 <p>Other arguments can be used to select a more specific entity and to control
136 </p>
138 <p>An implementation may ignore unknown arguments.</p>
140 <p>Some parameters that are commonly supported are described for service
142 </p>
143 <p>One notable difference exists for parameter <code>"Locale"</code>. For a
151 </p>
153 <p><member scope="com::sun::star::lang">XMultiServiceFactory::createInstance()</member>
159 </p>
166 <p>The owner of the provider may dispose of this object
168 </p>
170 <p>Views created by the provider generally refer to data that is managed by
174 </p>