Methods' Details |
getContext
- Description
- returns the underlying deployment context.
- Returns
- underlying deployment context
|
|
getSupportedPackageTypes
|
createAbortChannel
- Description
- creates a command channel to be used to asynchronously abort a command.
- Returns
- abort channel
|
|
addPackage
- Description
- adds an UNO package.
- Parameter url
- package URL, must be UCB conform
- Parameter mediaType
- media-type of package, empty string if to be detected
- Parameter xAbortChannel
- abort channel to asynchronously abort the adding process,
or null
- Parameter xCmdEnv
- command environment for error and progress handling
- Returns
- XPackage handle
|
|
removePackage
- Description
- removes an UNO package.
- Parameter identifier
- package identifier
- Parameter fileName
- package file name
- Parameter xAbortChannel
- abort channel to asynchronously abort the removing process,
or null
- Parameter xCmdEnv
- command environment for error and progress handling
|
|
getDeployedPackage
- Description
- gets a deployed package.
- Parameter identifier
- package identifier
- Parameter fileName
- package file name
- Parameter xCmdEnv
- command environment for error and progress handling
- Returns
- XPackage handle
|
|
getDeployedPackages
- Description
- gets all currently deployed packages.
- Parameter xAbortChannel
- abort channel to asynchronously abort the removing process,
or null
- Parameter xCmdEnv
- command environment for error and progress handling
- Returns
- all currently deployed packages
|
|
reinstallDeployedPackages
- Description
- Expert feature: erases the underlying registry cache and reinstalls
all previously added packages. Please keep in mind that all
registration status get lost.
Please use this in case of suspected cache inconsistencies only.
- Parameter xAbortChannel
- abort channel to asynchronously abort the adding process
- Parameter xCmdEnv
- command environment for error and progress handling
|
|
isReadOnly
- Description
- indicates that this implementation cannot be used for tasks
which require write access to the location where the extensions
are installed.
Normally one would call a method and handle the exception
if writing failed. However, a GUI interface may need to know beforehand
if writing is allowed. For example, the Extension Manager dialog
needs to enable / disable the Add button depending if the user has
write permission. Only the XPackageManager implementation knows the
location of the installed extensions. Therefore it is not possible
to check "externally" for write permission.
|
|
Copyright © 2011, Oracle and/or its affiliates. All rights reserved. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.