You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (Jira)" <ji...@apache.org> on 2021/10/05 19:48:00 UTC

[jira] [Created] (JENA-2178) Genralize module loading and initialization.

Andy Seaborne created JENA-2178:
-----------------------------------

             Summary: Genralize module loading and initialization.
                 Key: JENA-2178
                 URL: https://issues.apache.org/jira/browse/JENA-2178
             Project: Apache Jena
          Issue Type: Improvement
    Affects Versions: Jena 4.2.0
            Reporter: Andy Seaborne
            Assignee: Andy Seaborne
             Fix For: Jena 4.3.0


Jena system initialization code in {{JenaSystem.init}} provides the way extra jars can wire themselves into Jena. Initialization happens as soon as any application code touches Jena.

The mechanism is a simple abstraction over {{java.util.ServiceLoader}}

A new use case is to use the same machinery but for loading modules into Fuseki (example: a Apache Kafka connector for receiving updates). This loading happens after a server is built so it is happens at a different point to Jena system init.

So separate the mechanism for module loading by interface from the specific use in {{JenaSystem}}. Use this, retaining compatibility, and allow a separate module load phase to be added to Fuseki.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)