[
https://issues.apache.org/jira/browse/FELIX-3869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Pierre De Rop updated FELIX-3869:
---------------------------------
Fix Version/s: dependencymanager.runtime-3.2.0
> Fragment support for DependencyManager-Component
> ------------------------------------------------
>
> Key: FELIX-3869
> URL: https://issues.apache.org/jira/browse/FELIX-3869
> Project: Felix
> Issue Type: Improvement
> Components: Dependency Manager
> Reporter: Tuomas Kiviaho
> Assignee: Pierre De Rop
> Fix For: dependencymanager.runtime-3.2.0
>
> Attachments: Activator.patch, DependencyManagerRuntime.patch
>
>
> I've a use case where fragment support would be most welcome when declaring
> dependencies.
> I propose that the 'DependencyManager-Component' header would cover fragments
> just like 'Service-Component' header does as per OSGI spec 112.4.1 Service
> Component Header. This is quite easily implemented when BundleWiring is
> supported although it would require shifting compilation to version 1.6.
> Current 1.5 version could use PackageAdmin.
> ***
> A Service-Component manifest header specified in a fragment is ignored by
> SCR. However, XML documents referenced by a bundle’s Service-Component
> manifest header may be contained in attached fragments.
> SCR must process each XML document specified in this header. If an XML
> document specified by the header cannot be located in the bundle and its
> attached fragments, SCR must log an error message with the Log Service, if
> present, and continue.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
