[
https://issues.apache.org/jira/browse/SLING-12849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18000677#comment-18000677
]
Carsten Ziegeler commented on SLING-12849:
------------------------------------------
Looks like a bug to me, not sure whether that is a tooling bug.
I assume both factory PIDs actually work?
If so, reducing it to one is a breaking change - as there might be users using
it.
> "Sling Configured Feature" exposed via two different factory PIDs
> -----------------------------------------------------------------
>
> Key: SLING-12849
> URL: https://issues.apache.org/jira/browse/SLING-12849
> Project: Sling
> Issue Type: Bug
> Components: Feature Flags
> Affects Versions: Feature Flags 1.2.2
> Reporter: Konrad Windszus
> Priority: Major
>
> The Felix Web Console (system/console/configMgr) exposes the configuration
> for
> https://github.com/apache/sling-org-apache-sling-featureflags/blob/master/src/main/java/org/apache/sling/featureflags/impl/ConfiguredFeature.java
> via two different factory PIDs:
> # org.apache.sling.featureflags.Feature
> # org.apache.sling.featureflags.impl.ConfiguredFeature
> Only the former seems to be desired according to
> https://sling.apache.org/documentation/the-sling-engine/featureflags.html.
> The reason is that the metatype resource in
> {{OSGI-INF/metatype/org.apache.sling.featureflags.impl.ConfiguredFeature$Config.xml}}
> has two separate designate elements:
> {code}
> <Designate factoryPid="org.apache.sling.featureflags.Feature">
> <Object
> ocdref="org.apache.sling.featureflags.impl.ConfiguredFeature$Config"/>
> </Designate>
> <Designate
> factoryPid="org.apache.sling.featureflags.impl.ConfiguredFeature">
> <Object
> ocdref="org.apache.sling.featureflags.impl.ConfiguredFeature$Config"/>
> </Designate>
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
