[ 
https://issues.apache.org/jira/browse/FELIX-6618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carsten Ziegeler closed FELIX-6618.
-----------------------------------

> Check relevant registration properties for whiteboard services
> --------------------------------------------------------------
>
>                 Key: FELIX-6618
>                 URL: https://issues.apache.org/jira/browse/FELIX-6618
>             Project: Felix
>          Issue Type: Improvement
>          Components: HTTP Service
>            Reporter: Carsten Ziegeler
>            Assignee: Carsten Ziegeler
>            Priority: Major
>             Fix For: http.base-4.2.8, http.base-5.0.4, http.bridge-4.2.10, 
> http.bridge-5.0.6, http.jetty-4.2.14, http.jetty-5.0.6
>
>
> The trackers for any whiteboard service always deactivate and activate the 
> corresponding service on a modified event. If now any property on a 
> whiteboard service changes, this causes the reactivation - which (especially 
> for servlet context helpers) can result in a lot of churn.
> We should rather see if relevant properties have been modified and only then 
> do the reactivation



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to