[ 
https://issues.apache.org/jira/browse/KARAF-602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Hendy Irawan updated KARAF-602:
-------------------------------

    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.

  was:
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 :

logs: (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.


> Exploded OSGi bundle deployment with META-INF/MANIFEST.MF is not consistent
> ---------------------------------------------------------------------------
>
>                 Key: KARAF-602
>                 URL: https://issues.apache.org/jira/browse/KARAF-602
>             Project: Karaf
>          Issue Type: Bug
>          Components: runtime
>    Affects Versions: 2.2.0
>         Environment: Ubuntu 10.10, java version "1.6.0_20" / OpenJDK Runtime 
> Environment (IcedTea6 1.9.7) (6b20-1.9.7-0ubuntu1) / OpenJDK Server VM (build 
> 19.0-b09, mixed mode), Linux annafi 2.6.35-29-generic-pae 
> #51+kamal~mjgbacklight4-Ubuntu SMP Mon Apr 18 20:46:42 UTC 2011 i686 GNU/Linux
>            Reporter: Hendy Irawan
>
> 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.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to