Show TOC

Procedure documentationReferencing Non-Existent Bundled Libraries Locate this document in the navigation structure

 

The Java EE 5 specification describes how the Class-path element in the manifest file of an application's module (a JAR format file described in the EAR's application.xml descriptor) is processed when such element is defined but contains a location of a bundled library that cannot be found in the application's archive. By default, the deployment of such applications is rejected because of the unresolved bundled libraries.

Additionally, you can specify the requirements based on which to find the improper Class-Path element as acceptable or shall abort the deployment.

Caution Caution

This option allows deployment to finish successfully. However, if an application requests classes from these nonexistent bundled libraries in runtime, the requesting application will fail.

End of the caution.

To allow deployment to finish even though one or more of the referenced bundled libraries is not present:

  • the EAR of the application should/must contain a descriptor file application-service.xml in its META-INF folder

  • the descriptor should have the tag suppress_errors with attribute manifest_classpath_error = true.

In all other cases, the deployment will not finish successfully if a referenced bundled library is not in the application archive.

Procedure

  1. Add the SAP Application Library Container facet to your project.

  2. Edit theapplication-service.xml. For more information about the structure of the file, see: application-service.dtd