[
https://issues.apache.org/jira/browse/FELIX-6706?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler resolved FELIX-6706.
-------------------------------------
Resolution: Fixed
Added new framework property "org.apache.felix.http.require.config" which can
be set to true to avoid this situation.
https://github.com/apache/felix-dev/commit/2eb711b5c2e79d6e089725b3463f4fd661cd93f1
> Avoid Jetty restart in case of a required configuration
> -------------------------------------------------------
>
> Key: FELIX-6706
> URL: https://issues.apache.org/jira/browse/FELIX-6706
> Project: Felix
> Issue Type: Improvement
> Components: HTTP Service
> Reporter: Carsten Ziegeler
> Assignee: Carsten Ziegeler
> Priority: Major
> Fix For: http.jetty12-1.0.6, http.jetty-5.1.14
>
>
> If Jetty is configured through an OSGi configuration (singleton not factory),
> then Jetty is restarted. In this case, Jetty is first started with the
> default properties, then a managed service is registered which then later on
> is triggered by the OSGi configuration. And that results in Jetty restarting.
> While this works, it is unnecessary
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
