You deployed a Java EE Shared Library and want to use it from an application that is also deployed on the same cluster. Which two manifest attributes…

When an application that

a shared library or package is deployed, WebLogic Server checks

the names and version string requirements against the libraries registered with the server. If an exact

match for a library or package name is not found, or if the version requirements are not met, the

application deployment fails.

If WebLogic Server finds a name and version string match for all of the libraries referenced in the

application, the server adds the libraries' classes to the classpath of the referencing application and

merges deployment descriptors from both the application and libraries in memory. The resulting

deployed application appears as if the referenced libraries were bundled with the application itself.

Note:

As a best practice, your development team should always include version string information for a

library or optional package in the manifest file for the deployment. See Editing Manifest Entries for

Shared Libraries in Developing Applications for Oracle WebLogic Server for more information.

If you are deploying a library or package that does not include version string information, you can

specify it at the command line using one or both of the following options:

libspecver—Defines a specification version for the library or package.

libimplver—Specifies an implementation version for the library or package.

Reference: Deploying Applications to Oracle WebLogic Server, Deploying Shared Java EE Libraries and

Dependent Applications