The parameter aServiceSpecifier passed to
::com::sun::星／主役にする::lang::XMultiServiceFactory::createInstanceWithArguments()
supports at least the service specifiers
"com.sun.星／主役にする.configuration.ConfigurationAccess" and
"com.sun.星／主役にする.configuration.ConfigurationUpdateAccess".
Using the first of these service specifiers requests a read-only 見解（をとる） of
the configuration.
The 反対する that is created 器具／実施するs service ConfigurationAccess.
To 反映する its element 役割 as root of the 見解（をとる）, it 器具／実施するs
service AccessRootElement.
Using the second form requests an updatable 見解（をとる） of the configuration.
The 反対する that is created should 器具／実施する service
ConfigurationUpdateAccess. To 反映する its element 役割
which 含むs controlling updates for the whole 見解（をとる）, it 器具／実施するs
service UpdateRootElement.
If the root element of the 見解（をとる） is 示すd read-only (as 示すd
by PropertyAttributes::READONLY),
the 実施 may either raise an exception or return a (read-only)
ConfigurationAccess/AccessRootElement instead.
The arguments passed to
::com::sun::星／主役にする::lang::XMultiServiceFactory::createInstanceWithArguments()
in parameter aArguments 明示する the 見解（をとる） of the configuration that
should be created. That is, they 決定する the subset of elements that can be
接近d starting from the returned 反対する. Each element of the argument
sequence should be a ::com::sun::星／主役にする::beans::PropertyValue
or a ::com::sun::星／主役にする::beans::NamedValue,
so that the parameters can be identified by 指名する rather than by position.
What combinations of arguments are supported depends on the service 指名する.
With both of the 基準 service-specifiers above, an 実施 must
受託する a 選び出す／独身 argument 指名するd nodepath of type string.
This argument must 含む／封じ込める the 絶対の path to an element of the
configuration. The 見解（をとる） that is selected consists of the 指名するd element and
all its decendants.
Other arguments can be used to 支配（する）／統制する the 行為 of the 見解（をとる）. These
are different for different 実施s. Whether and how they are used
may also depend on the configuration 蓄える／店 and configuration that were
selected when the provider was created.
An 実施 must ignore unknown arguments.
Some parameters that are 一般的に supported are:
-
Selecting data into a 見解（をとる）:
"nodepath" : string- 明示するs the 場所 of the 見解（をとる） root in the configuration.
"depth" : short- 明示するs that elements of the 階層制度 that are more than the given
number of nesting levels away from the root need not be 含むd in the
見解（をとる）.
"地元の" : ::com::sun::星／主役にする::lang::地元の- 明示するs the 地元の for which localized values should be
retrieved.
Example: In the 階層制度
A - B1 - C1
|
- B2 - C2 (localized: de, en, fr, ..)
| |
| - C3 - D1
| | |
| | - D2 - E1
| |
| - C4 - D3 - E2 - F1
| | |
| | - F2
| |
| - C5
|
- B3
|
- B4 - C6 - D4 - E3
selecting a 見解（をとる） with nodepath = "/A/B2",
depth = 2 and 地元の = <地元の for en_US>
would result in the tree fragment
(A-) B2 - C2 (en)
|
- C3 - D1
| |
| - D2 (..)
|
- C4 - D3 (..)
|
- C5
-
Controlling （武器などの）隠匿場所 行為: (with providers that
（武器などの）隠匿場所 configuration data)
"enableasync" : boolean- 支配（する）／統制するs how updates are 扱うd in the （武器などの）隠匿場所. If true, the
（武器などの）隠匿場所 may operate in 令状-支援する 方式, where updates at
first only 影響する／感情 the （武器などの）隠匿場所 and are written to 執拗な 貯蔵
at some later time. If 誤った, the （武器などの）隠匿場所 must operate in
令状-through 方式, where updates are written to 執拗な
貯蔵 at once - that is before
::com::sun::星／主役にする::util::XChangesBatch::commitChanges()
returns.
This parameter was 以前は called "lazywrite".
The old 指名する should still be supported for compatibility.
"nocache" : boolean- This deprecated parameter
明示するs that data for the 見解（をとる） is not taken from the （武器などの）隠匿場所, but
read 直接／まっすぐに from 貯蔵. This may entail that 未来 changes that
become 明白な in the （武器などの）隠匿場所 are not 反映するd in this 見解（をとる） and that
changes done through this 見解（をとる） are not 反映するd in the （武器などの）隠匿場所.
Use with 警告を与える !
This parameter is not supported by all 実施s and may be
silently ignored !
::com::sun::星／主役にする::lang::XMultiServiceFactory::createInstance()
may be unusable. Only an 実施 that supports service 指名するs that can be
used with no その上の arguments support this method. It should return the
same result as if
::com::sun::星／主役にする::lang::XMultiServiceFactory::createInstanceWithArguments()
had been called using an empty sequence of arguments.
