You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@stanbol.apache.org by "Rupert Westenthaler (JIRA)" <ji...@apache.org> on 2013/12/17 12:11:06 UTC

[jira] [Created] (STANBOL-1239) EngineTracker and ChainTracker should lazily start tracking

Rupert Westenthaler created STANBOL-1239:
--------------------------------------------

             Summary: 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.



--
This message was sent by Atlassian JIRA
(v6.1.4#6159)