[
https://issues.apache.org/jira/browse/FELIX-2895?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13013636#comment-13013636
]
Justin Edelson commented on FELIX-2895:
---------------------------------------
Richard - the key difference is that getResource() returns exactly one result.
findEntries returns all matching results.
The use case I'm concerned with is where there is more than one Service
Component file. Sorry if this wasn't clear.
> Allow the use of a property to tell SCR to always use findEntries, not
> getResource
> ----------------------------------------------------------------------------------
>
> Key: FELIX-2895
> URL: https://issues.apache.org/jira/browse/FELIX-2895
> Project: Felix
> Issue Type: Improvement
> Reporter: Justin Edelson
> Attachments: FELIX-2895.patch
>
>
> The current version of SCR will use the API method getResource() to get the
> service component descriptor if the Service-Component header does not contain
> a wildcard. This precludes the discovery of DS components in attached
> fragment bundles. From the DS spec:
> Section 112.4:
> Component descriptions are defined in XML documents contained in a bundle
> and any attached fragments.
> Section 112.4.1:
> The last component of each path in the Service-Component header may use
> wildcards so that Bundle.findEntries can be used to locate the XML document
> within the bundle and its fragments....
> A Service-Component manifest header specified in a fragment is ignored by
> SCR. However, XML documents referenced by a bundle's Service-Component
> Note the use of the word "may" in the first sentence. It does not say that
> findEntries() should/must *only* be used if there's a wildcard.
> As such, I believe this is within the spec, albeit not backwards compatible
> which is why I'm proposing to use a framework property.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
