[FELIX-518] Wrong processing order of Localization-, Bundle and Processed-Resources

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Fix Version/s: deploymentadmin-0.9.8
• Component/s: Deployment Admin
• Environment: Maven version: 2.0.8; Java version: 1.6.0_04; OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
• Assignee: J.W. Janssen
• Reporter: Siamak Haschemi
• Created: 15/Mar/08 23:01
• Updated: 16/Jan/16 15:03
• Resolved: 14/Jan/16 16:21

Description

The DeploymentAdmin specification defines in Section 114.3 (File Format), Page 340 and 341, the order of resources in the Jar as follows:

1 META-INF/MANIFEST.MF
2 META-INF/.SF, META-INF/.DSA, META-INF/*.RS
3 Localization files
4 Bundles
5 Resources

The current DeploymentAdmin implementation processes the contents of the JarInputStream with the UpdateCommand (handles bundles) and the ProcessResourceCommand (handles resources). If the Jar contains Localization-Resources (which are placed before any other resource or bundle) the UpdateCommand failes, because assumes that the Bundles come at first in the JarInputStream.

As a result a DeploymentException with the message "Resource '...' is not described in the manifest." is thrown.

Kind regards,

Siamak Haschemi