[
https://issues.apache.org/jira/browse/SLING-6586?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seifert closed SLING-6586.
---------------------------------
> osgi-mock: Loading SCR metadata fails for components with name != class name
> ----------------------------------------------------------------------------
>
> Key: SLING-6586
> URL: https://issues.apache.org/jira/browse/SLING-6586
> Project: Sling
> Issue Type: Bug
> Components: Testing
> Affects Versions: Testing OSGi Mock 1.9.2, Testing OSGi Mock 2.2.2
> Reporter: Stefan Seifert
> Assignee: Stefan Seifert
> Labels: mocks
> Fix For: Testing OSGi Mock 2.2.4, Testing OSGi Mock 1.9.4
>
>
> in most cases the xml file name for the SCR metadata is the same as the
> implementation class name. but this is not the case when the component
> defines a different component name - example:
> [ResourceResolverFactoryActivator.java|https://github.com/apache/sling/blob/trunk/bundles/resourceresolver/src/main/java/org/apache/sling/resourceresolver/impl/ResourceResolverFactoryActivator.java].
> in this case there is no relation between implementation class name and xml
> file name, and the component cannot be used with osgi-mock.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
