Installed optional packages

Installed optional packages

+
Search Tips | Advanced Search

Installed optional packages enable applications to use the classes in Java archive (.jar) files without having to include them explicitly in a class path. An installed optional package is a .jar file containing specialized tags in its manifest file that enable the appserver to identify it. An installed optional package declares one or more shared library .jar files in the manifest file of an application. When the application is installed on a server or cluster, the classes represented by the shared libraries are loaded in the class loader of the application, making the classes available to the application.
When a J2EE application is installed on a server or cluster, dependency information is specified in its manifest file. WAS reads the dependency information of the application (.ear file) to automatically associate the application with an installed optional package .jar file. WAS adds the .jar files in associated optional packages to the application class path. Classes in the installed optional packages are then available to application classes.
Installed optional packages used by WAS are described in section 8.2 of the J2EE specification, V1.4.
WAS supports using the manifest file (manifest.mf) in shared library .jar files and application .ear files.
WAS does not support the J2SE Installed Optional Package semantics, which primarily serve the applet environment. WAS ignores applet-specific tags within manifest files.

Sample manifest.mf file

A sample manifest file follows for an application app1.ear that refers to a single shared library file util.jar:
 app1.ear:
    META-INF/application.xml
    ejb1.jar:
         META-INF/MANIFEST.MF:
             Extension-List: util
             util-Extension-Name: com/example/util
             util-Specification-Version: 1.4
         META-INF/ejb-jar.xml


util.jar:
    META-INF/MANIFEST.MF:
        Extension-Name: com/example/util
        Specification-Title: example.com's util package
        Specification-Version: 1.4
        Specification-Vendor: example.com
        Implementation-Version: build96
The syntax of a manifest entry depends on whether the entry applies to a member with a defining role (the shared library) or a member with a referencing role (a J2EE application or a module within a J2EE application).

Manifest entry tagging

Main tags used for manifest entries include...

Extension-List

A required tag with variable syntax.
Within the context of the referencing role (application's manifest), this is a space delimited list that identifies and constructs unique Extension-Name, Extension-Specification tags for each element in the list. Within the context of the defining role (shared library), this tag is not valid.

Extension-Name

A required tag that provides a name and links the defining and referencing members.
The syntax of the element within the referencing role is to prefix the element with the <ListElement> string. For each element in the Extension-List, there is a corresponding <ListElement>-Extension-Name tag. The defining string literal value for this tag (in the above sample com/example/util1) is used to match (in an equality test) the corresponding tags between the defining and referencing roles.

Specification-V

A required tag that identifies the specification version and links the defining and referencing members.

Implementation-V

An optional tag that identifies the implementation version and links the defining and referencing members.

Further information on these tags is in the .jar file specification.

Related concepts
Class loaders

Related tasks
Use installed optional packages
Manage shared libraries