Alliance* http://www.osgi.org/*
**hargr...@us.ibm.com* hargr...@us.ibm.com
office: +1 386 848 1781
mobile: +1 386 848 3788
From:Carl Hall c...@hallwaytech.com
To:osgi-dev@mail.osgi.org,
Date:2012/01/23 11:01
Subject:[osgi-dev] Services from a Fragment
:Re: [osgi-dev] Services from a Fragment Bundle
Sent by:osgi-dev-boun...@mail.osgi.org
If more than 1 fragment attaches to a host bundle and each of those
fragments has a service components file (defined in host but lives in
fragment), will each fragment's service components file
Subject:Re: [osgi-dev] Services from a Fragment Bundle
Sent by:osgi-dev-boun...@mail.osgi.org
--
If more than 1 fragment attaches to a host bundle and each of those
fragments has a service components file (defined in host but lives in
fragment
11:29
Subject:Re: [osgi-dev] Services from a Fragment Bundle
Sent by:osgi-dev-boun...@mail.osgi.org
Unfortunately, the spec isn't entirely clear about this in the case where
wildcards were *not* used. See
https://issues.apache.org/jira/browse/FELIX-2895
Justin
On Fri, Jan 27
I have an interesting scenario that I would love some clarity on. I see
components avaiilable from a fragment bundle and I'm wondering if
declarative services is to blame/reward.
A third party library I use has the following setup: a host bundle with
core-serviceComponents.xml and a fragment
This is correct/expected behaviour.
The Service-Component header is ignored if it appears in the manifest
of a fragment, however the XML descriptor can appear in a fragment if
it is referenced from the Service-Component header in the manifest of
its host bundle.
See section 112.4.1 of the
You are a gentleman and a scholar. Thanks, Neil!
On Mon, Jan 23, 2012 at 11:03 AM, Neil Bartlett njbartl...@gmail.comwrote:
This is correct/expected behaviour.
The Service-Component header is ignored if it appears in the manifest
of a fragment, however the XML descriptor can appear in a
