[
https://issues.apache.org/jira/browse/SLING-6659?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15931718#comment-15931718
]
Konrad Windszus commented on SLING-6659:
----------------------------------------
In OSGi Comp R6, 112.5.10 it says about bound service replacement:
bq. If a component configuration has a static reference and a bound service is
modified or unregistered and ceases to be a target service, or the
policy-option is greedy and a better target service becomes available then SCR
must deactivate the component configuration. Afterwards, SCR must attempt to
activate the component configuration again if another target service can be
used as a replacement for the outgoing service.
It is not 100% clear from that sentence but I would interpret it like this:
bq. If a component configuration has a static reference and a bound service is
modified ... then SCR must deactivate the component configuration. Afterwards,
SCR must attempt to activate the component configuration again if another
target service can be used as a replacement for the outgoing service.
> ValidationModelRetrieverImpl does not respect changes to Validator's service
> properties
> ---------------------------------------------------------------------------------------
>
> Key: SLING-6659
> URL: https://issues.apache.org/jira/browse/SLING-6659
> Project: Sling
> Issue Type: Bug
> Components: Extensions, Validation
> Reporter: Oliver Lietz
>
> {{ValidationModelRetrieverImpl}} is using service properties of validators
> (service ranking and validator id) to set up a list (map) of known
> validators, but is agnostic to changes happening at runtime. The list is
> built only on validator activation/deactivation but not on modification.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
