[
https://issues.apache.org/jira/browse/KARAF-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nicolas Brasey updated KARAF-5299:
----------------------------------
Description:
When installing a fragment bundle with the command bundle:install, the fragment
does not get bound to its host. The fragment is bound correctly after a restart
of karaf.
Workaround:
Install the fragment bundle with the deploy directory.
EDIT:
I did more tests, and found another inconsistency when uninstalling the
fragment. So here a more detailed scenario:
When installing the fragment:
a) the fragment is not automatically bound to the host
b) Then, if I update the host, the fragment is bound correctly (Like Achim
suggested)
When uninstalling the fragment:
a) the host is still bound to the fragment, see below. As you can see, the
host bundle id 279 is bound to the fragments bundle id 280 which is not there
any more
279 │ Active │ 80 │ 1.10.0.SNAPSHOT │
dms-profiles-mgmt-impl, Fragments: 280
karaf@root()>
b) Then, if I update the host, the fragment is still bound.
was:
When installing a fragment bundle with the command bundle:install, the fragment
does not get bound to its host. The fragment is bound correctly after a restart
of karaf.
Workaround:
Install the fragment bundle with the deploy directory.
> fragment bundle not bound to its host when using the command bundle:install
> ---------------------------------------------------------------------------
>
> Key: KARAF-5299
> URL: https://issues.apache.org/jira/browse/KARAF-5299
> Project: Karaf
> Issue Type: Bug
> Affects Versions: 4.1.2
> Reporter: Nicolas Brasey
> Fix For: 4.1.3
>
>
> When installing a fragment bundle with the command bundle:install, the
> fragment does not get bound to its host. The fragment is bound correctly
> after a restart of karaf.
> Workaround:
> Install the fragment bundle with the deploy directory.
> EDIT:
> I did more tests, and found another inconsistency when uninstalling the
> fragment. So here a more detailed scenario:
> When installing the fragment:
> a) the fragment is not automatically bound to the host
> b) Then, if I update the host, the fragment is bound correctly (Like Achim
> suggested)
> When uninstalling the fragment:
> a) the host is still bound to the fragment, see below. As you can see, the
> host bundle id 279 is bound to the fragments bundle id 280 which is not there
> any more
> 279 │ Active │ 80 │ 1.10.0.SNAPSHOT │
> dms-profiles-mgmt-impl, Fragments: 280
> karaf@root()>
> b) Then, if I update the host, the fragment is still bound.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
