Spiegazione | An application manifest, APPLICATION.MF, must contain both Application-SymbolicName and Application-Version headers. |
Azione | Edit the APPLICATION.MF file to add the missing header or headers. |
Spiegazione | The Deployed-Content header in the deployment manifest, DEPLOYMENT.MF, is not valid. |
Azione | If you provided this file, correct the contents of the Deployed-Content header. |
Spiegazione | The application content is ambiguous or not valid. |
Azione | Check and correct the source of the content, if possible. |
Spiegazione | A deployment manifest, DEPLOYMENT.MF file, must contain a valid deployed-version header. |
Azione | If you provided the DEPLOYMENT.MF file, check that it contains a valid deployed-version header. |
Spiegazione | A service has been declared with a filter expression that is not valid. |
Azione | Locate and correct the filter expression. |
Spiegazione | A bundle manifest cannot be extracted because the location is not a valid file or directory. |
Azione | If you provided this location, check that it is valid and that it exists. |
Spiegazione | A bundle manifest cannot be processed because at least one element does not contain a required quotation mark. |
Azione | Locate and correct the specified bundle manifest. |
Spiegazione | A manifest header cannot be parsed because it contains a version attribute that is not valid. |
Azione | Locate and correct the version according to the OSGi version specification. |
Spiegazione | A manifest header cannot be parsed because it contains an empty version attribute. |
Azione | Locate and correct the relevant header. |
Spiegazione | A file that must contain exact versions only, such as a deployment manifest, DEPLOYMENT.MF, contains a range of versions. |
Azione | Locate and correct the relevant header. |
Spiegazione | The product needs to create a temporary directory but cannot. |
Azione | Check that storage space exists, and that the product has the necessary permissions to create the directory. |
Spiegazione | An entry in the Import-Service header of the application manifest, APPLICATION.MF, is not valid. |
Azione | Locate and correct the relevant header. |
Spiegazione | An entry in the Export-Service header of the application manifest, APPLICATION.MF, is not valid. |
Azione | Locate and correct the relevant header. |
Spiegazione | An entry in the Application-Roles header of the application manifest, APPLICATION.MF, is not valid. |
Azione | Locate and correct the relevant header. |
Spiegazione | This exception is unexpected. The cause is not immediately known. |
Azione | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Spiegazione | This exception is unexpected. The cause is not immediately known. |
Azione | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Spiegazione | The Deployed-Use-Bundle header in the deployment manifest, DEPLOYMENT.MF is not valid. |
Azione | If you provided this file, correct the contents of the Use-Bundle header. |
Spiegazione | The Provision-Bundle header in the deployment manifest, DEPLOYMENT.MF is not valid. |
Azione | If you provided this file, correct the contents of the Provision-Bundle header. |
Spiegazione | Two Web application bundle (WAB) files in the enterprise bundle archive (EBA) file have the same bundle symbolic name, version, and Web-ContextPath. |
Azione | Ensure that the EBA file contains the correct WAB files. |
Spiegazione | A bundle file in the enterprise bundle archive (EBA) file has no bundle manifest, MANIFEST.MF. This bundle cannot serve Web content and might not operate correctly. |
Azione | Ensure that the bundle file contains a valid bundle manifest file. |
Spiegazione | This exception is unexpected. The cause is not immediately known. |
Azione | If the problem persists, see problem determination information on the WebSphere Application Server Support page at http://www.ibm.com/software/webservers/appserv/was/support/. |
Spiegazione | The bundle manifest, MANIFEST.MF, for a bundle in the enterprise bundle archive (EBA) file cannot be read. This bundle cannot serve Web content and might not operate correctly. |
Azione | Ensure that the bundle file contains a valid manifest file. |
Spiegazione | The DeployedService-Import header in a deployment manifest, DEPLOYMENT.MF, is not valid. |
Azione | If you provided the deployment manifest, correct the contents of the DeployedService-Import header. |
Spiegazione | The bundles listed in the Deployed-Content header in the DEPLOYMENT.MF file must match the bundles listed in the Application-Content header in the APPLICATION.MF file. The bundle version in the Deployed-Content header in the DEPLOYMENT.MF file must be within the version range for the corresponding bundle in the Application-Content header in the APPLICATION.MF file. |
Azione | If you provided the deployment manifest, correct the contents of the Deployed-Content header in the DEPLOYMENT.MF file. Ensure that each bundle is listed in both the Deployed-Content header in the DEPLOYMENT.MF file and the Application-Content header in the APPLICATION.MF file, and that the bundle version in the Deployed-Content header in the DEPLOYMENT.MF file is within the version range for the corresponding bundle in the Application-Content header in the APPLICATION.MF file. |
Spiegazione | The bundles listed in the Deployed-Use-Bundle header in the DEPLOYMENT.MF file must also be listed in the Use-Bundle header in the APPLICATION.MF file. The bundle version in the Deployed-Use-Bundle header in the DEPLOYMENT.MF file must be within the version range for the corresponding bundle in the Use-Bundle header in the APPLICATION.MF file. The Use-Bundle header in the APPLICATION.MF file can list additional bundles that are not listed in the Deployed-Use-Bundle header of the DEPLOYMENT.MF file. |
Azione | If you provided the deployment manifest, correct the contents of the Deployed-Use-Bundle header in the DEPLOYMENT.MF file. Ensure that each bundle listed in the Deployed-Use-Bundle header in the DEPLOYMENT.MF file is also listed in the Application-Content header of the APPLICATION.MF file, and that the bundle version in the Deployed-Use-Bundle header of the DEPLOYMENT.MF file is within the version range for the corresponding bundle in the Use-Bundle header in the APPLICATION.MF file. |
Spiegazione | The WAS-Feature-Required header in the deployment manifest, DEPLOYMENT.MF, is not valid. |
Azione | If you provided the deployment manifest, correct the contents of the WAS-Feature-Required header. |
Spiegazione | The Application-SymbolicName in the application manifest, APPLICATION.MF, and deployment manifest, DEPLOYMENT.MF, do not match. |
Azione | Check that the correct file is provided, and ensure the values of Application-SymbolicName in the APPLICATION.MF and DEPLOYMENT.MF are the same. |
Spiegazione | The Application-Version in the application manifest, APPLICATION.MF, and deployment manifest, DEPLOYMENT.MF, do not match. |
Azione | Check that the correct file is provided, and ensure the values of Application-Version in the APPLICATION.MF and DEPLOYMENT.MF are the same. |
Spiegazione | The Application-SymbolicName and Application-Version in the application manifest, APPLICATION.MF, and deployment manifest, DEPLOYMENT.MF, do not match. |
Azione | Check that the correct file is provided, and ensure the values of Application-SymbolicName and Application-Version in the APPLICATION.MF and DEPLOYMENT.MF are the same. |