An application that needs to use a shared library has a deployment descriptor that only specifies the SpecificationVersion and ExtensionName of the shared library. When the application is deployed…

Question

Options

• AThe application will go into an ADMIN state and fail to deploy because the Implementation
• BThe application will be deployed but the classes in the shared library will not be available.
• CIf you are using the WebLogic Admin Console, you will be prompted for the version you want to
• DIf there are multiple versions of the shared library deployed, WebLogic will use the one with the
• EIf there are multiple versions of the shared library deployed, WebLogic will use the one that was

• A
  14% (3)
• C
  5% (1)
• D
  76% (16)
• E
  5% (1)

Explanation

An internal application may be configured to always use a minimum version of the same library. Applications that require no specific version can be configured to use the latest version of the * SpecificationVersion (a manifest Attributes for Java EE Libraries) An optional String value that defines the specification version of the shared Java EE library. Referencing applications can optionally specify a required SpecificationVersion for a library; if the exact specification version is not available, deployment of the referencing application fails. The SpecificationVersion uses the following format: Major/minor version format, with version and revision numbers separated by periods (such as Referencing applications can be configured to require either an exact version of the shared Java EE library, a minimum version, or the latest available version. * ImplementationVersion (a manifest Attributes for Java EE Libraries) An optional String value that defines the code implementation version of the shared Java EE library. You can provide an ImplementationVersion only if you have also defined a SpecificationVersion. * ExtensionName (a manifest Attributes for Java EE Libraries) An optional string value that identifies the name of the shared Java EE library. Referencing applications must use the exact ExtensionName value to use the library. As a best practice, always specify an ExtensionName value for each library. If you do not specify an extension name, one is derived from the deployment name of the library. Default deployment names are different for archive and exploded archive deployments, and they can be set to arbitrary values in the deployment command. * After a library is deployed, the extensionname, specificationversion and implementationversion of the library can be found in Administration console.

No community discussion yet for this question.