[
https://issues.apache.org/jira/browse/FELIX-6565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17608660#comment-17608660
]
Amit Mondal commented on FELIX-6565:
------------------------------------
It seems it would be difficult to implement a strategy to conditionally
activate the components that depend on _*org.osgi.service.http*_ and
_*org.osgi.service.http.context.*_ My idea was to make the components
mandatorily depend on two PIDs one of which would only be created if the
aforementioned OSGi HTTP packages are wired to the HealthCheck core bundle.
Since, the components use metatype, we cannot provide a different PID for the
components to depend on.
> Make OSGi HTTP Package dependency optional in HealthCheck core bundle
> ---------------------------------------------------------------------
>
> Key: FELIX-6565
> URL: https://issues.apache.org/jira/browse/FELIX-6565
> Project: Felix
> Issue Type: Improvement
> Components: Health Checks
> Reporter: Amit Mondal
> Priority: Minor
> Labels: easyfix
>
> Currently, the Felix HealthCheck core bundle mandatorily imports
> org.osgi.service.http package which is used by
> {_}*HealthCheckExecutorServlet*{_}. In our current system, we don't use HTTP
> at all, hence, neither _*javax.servlet*_ nor _*org.osgi.service.http*_ is
> available in the runtime. Hence, the health checks don't work as it
> mandatorily requires _*org.osgi.service.http*_ package dependency. Since,
> _*HealthCheckExecutorServlet*_ is not a core component for the health checks,
> we can consider the following options:
> # Provide a separate bundle with HTTP dependency (invasive approach)
> # Make _*org.osgi.service.http*_ an optional package for HealthCheck core
> and conditionally enable _*HealthCheckExecutorServlet*_ component if
> _*org.osgi.service.http*_ is wired to the HealthCheck core bundle (similar
> approach we did for Quartz to check the availability of Quartz in runtime)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
