Uploaded image for project: 'Felix'
  1. Felix
  2. FELIX-518

Wrong processing order of Localization-, Bundle and Processed-Resources

VotersWatch issueWatchersLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • None
    • deploymentadmin-0.9.8
    • Deployment Admin
    • None
    • Maven version: 2.0.8
      Java version: 1.6.0_04
      OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"

    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

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            jajans J.W. Janssen
            siamak Siamak Haschemi
            Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment