karaf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Guillaume Nodet (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KARAF-5299) fragment bundle not bound to its host when using the command bundle:install
Date Wed, 25 Oct 2017 08:04:00 GMT

    [ https://issues.apache.org/jira/browse/KARAF-5299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16218234#comment-16218234
] 

Guillaume Nodet commented on KARAF-5299:
----------------------------------------

In this case, there's also the fact that fragments do not behave like standard bundles, i.e.
you can't resolve them explicitely, they are always resolved as part of their host and the
user can't unresolve a fragment either: if it's installed, if will always be resolved with
its host.  But that's how the spec work.

For the {{bundle:install}} command, we could think about displaying a message to the user
telling him to run a {{bundle:refresh}} command if that's necessary...

> 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
>            Assignee: Jean-Baptiste Onofré
>
> 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  
> {code}
> 279 │ Active │  80 │ 1.10.0.SNAPSHOT                    │ dms-profiles-mgmt-impl,
Fragments: 280
> karaf@root()>     
> {code}
> b) Then, if I update the host, the fragment is still bound.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message