Uploaded image for project: 'Karaf'
  1. Karaf
  2. KARAF-602

Exploded OSGi bundle deployment with META-INF/MANIFEST.MF is not consistent

    Details

    • Type: Bug
    • Status: Open
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 2.2.0
    • Fix Version/s: None
    • Component/s: karaf-osgi
    • Labels:
      None
    • Environment:

      Description

      When deploying an OSGi bundle with OSGI-INF/blueprint/something.xml by copying the JAR file to deploy/, it works.

      However:
      1. Copying the contents excluding META-INF/MANIFEST.MF to deploy/<somedir>, it works
      2. Copy META-INF/MANIFEST.MF to deploy/<somedir>/META-INF/MANIFEST.MF, it doesn't work

      By it doesn't work, meaning the previous bundle (in step 1) is uninstalled, but the new (i.e. updated) bundle is not resolved, not active, not installed at all.

      logs is not helpful: (level is TRACE)

      03:42:21,508 | DEBUG | lixDispatchQueue | framework | ? ? | 0 - org.apache.felix.framework - 3.0.8 | FrameworkEvent PACKAGES REFRESHED
      03:42:21,508 | DEBUG | lixDispatchQueue | framework | ? ? | 0 - org.apache.felix.framework - 3.0.8 | FrameworkEvent PACKAGES REFRESHED

      The same thing happens when the order is reversed:
      1. Delete deploy/<somedir> so we get a "clean start"
      2. Copying the contents including META-INF/MANIFEST.MF to deploy/<somedir>, it works
      3. Delete deploy/<somedir>/META-INF/MANIFEST.MF, it doesn't work

      Seems like the exploded bundle undeployer left it in an inconsistent state.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                ceefour Hendy Irawan
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated: