[
https://issues.apache.org/jira/browse/STANBOL-1239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rupert Westenthaler updated STANBOL-1239:
-----------------------------------------
Description:
In the trunk version there are some NPE caused by the OSGI service factory
returning null. This is cause by ServiceTrackers that are opened within the
activate method. While those NPE do not have any functional consequences (OSGI
is catching them and will repeat calls to addService(..) later on) they can be
easily avoided by only start tracking on the first request to the EngineTracker
and ChainTracker methods.
NOTE: this only affects the trunk and does not appear in 0.12
was:In the trunk version there are some NPE caused by the OSGI service
factory returning null. This is cause by ServiceTrackers that are opened within
the activate method. While those NPE do not have any functional consequences
(OSGI is catching them and will repeat calls to addService(..) later on) they
can be easily avoided by only start tracking on the first request to the
EngineTracker and ChainTracker methods.
> EngineTracker and ChainTracker should lazily start tracking
> -----------------------------------------------------------
>
> Key: STANBOL-1239
> URL: https://issues.apache.org/jira/browse/STANBOL-1239
> Project: Stanbol
> Issue Type: Improvement
> Reporter: Rupert Westenthaler
> Assignee: Rupert Westenthaler
> Priority: Minor
>
> In the trunk version there are some NPE caused by the OSGI service factory
> returning null. This is cause by ServiceTrackers that are opened within the
> activate method. While those NPE do not have any functional consequences
> (OSGI is catching them and will repeat calls to addService(..) later on) they
> can be easily avoided by only start tracking on the first request to the
> EngineTracker and ChainTracker methods.
> NOTE: this only affects the trunk and does not appear in 0.12
--
This message was sent by Atlassian JIRA
(v6.1.4#6159)
