[ https://issues.apache.org/jira/browse/JENA-2178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425511#comment-17425511 ]
ASF subversion and git services commented on JENA-2178: ------------------------------------------------------- Commit 02d01792e936555ce9dcfeae8d47886fe6b69659 in jena's branch refs/heads/main from Andy Seaborne [ https://gitbox.apache.org/repos/asf?p=jena.git;h=02d0179 ] JENA-2178: Generalize service loading > Generalize 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 > Priority: Minor > 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)