Mailing-List: contact issues-help@karaf.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@karaf.apache.org
Date: Wed, 25 Oct 2017 07:46:00 +0000 (UTC)
From: "Guillaume Nodet (JIRA)" <jira@apache.org>
To: issues@karaf.apache.org
Message-ID: <JIRA.13093511.1502291946000.53771.1508917560258@Atlassian.JIRA>
In-Reply-To: <JIRA.13093511.1502291946000@Atlassian.JIRA>
References: <JIRA.13093511.1502291946000@Atlassian.JIRA> <JIRA.13093511.1502291946906@jira-lw-us.apache.org>
Subject: [jira] [Commented] (KARAF-5299) fragment bundle not bound to its
 host when using the command bundle:install
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Wed, 25 Oct 2017 07:46:07 -0000


    [ https://issues.apache.org/jira/browse/KARAF-5299?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1621=
8218#comment-16218218 ]=20

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

This looks like the expected behavior to me.
That's what the OSGi specification says should happen, so there's not much =
to do here.

When installing bundles using the {{bundle:install}} command, you need to p=
erform a {{bundle:refresh}} at the end.  Deploy bundles using features or t=
he {{deploy}} directory will do that for you though.

> fragment bundle not bound to its host when using the command bundle:insta=
ll
> -------------------------------------------------------------------------=
--
>
>                 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=C3=A9
>             Fix For: 4.1.3
>
>
> When installing a fragment bundle with the command bundle:install, the fr=
agment does not get bound to its host. The fragment is bound correctly afte=
r 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 f=
ragment. 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 Achi=
m suggested)
> When uninstalling the fragment:
> a)  the host is still bound to the fragment, see below. As you can see, t=
he host bundle id 279 is bound to the fragments bundle id 280 which is not =
there any more =20
> {code}
> 279 =E2=94=82 Active =E2=94=82  80 =E2=94=82 1.10.0.SNAPSHOT             =
       =E2=94=82 dms-profiles-mgmt-impl, Fragments: 280
> karaf@root()>    =20
> {code}
> b) Then, if I update the host, the fragment is still bound.


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