- All Superinterfaces:
FusekiActionCycle
,FusekiBuildCycle
,FusekiStartStop
- All Known Subinterfaces:
FusekiAutoModule
A module is additional code, usually in a separate jar, but it can be part of the application code. Calls are made to each module at certain points in the lifecycle of a Fuseki server.
A module must provide a no-argument constructor if it is to be loaded automatically.
When a server is being built: *
- prepare(org.apache.jena.fuseki.main.FusekiServer.Builder, java.util.Set<java.lang.String>, org.apache.jena.rdf.model.Model)
-- called at the beginning of the
FusekiServer.Builder build()
step. This call can manipulate the server configuration. This is the usual operation for customizing a server. - configured(org.apache.jena.fuseki.main.FusekiServer.Builder, org.apache.jena.fuseki.server.DataAccessPointRegistry, org.apache.jena.rdf.model.Model) -- called after the DataAccessPoint registry has been built.
- server(FusekiServer) -- called at the end of the "build" step before
FusekiServer.Builder build()
returns.
- serverBeforeStarting(FusekiServer) -- called before
server.start
happens. - serverAfterStarting(FusekiServer) -- called after
server.start
happens. - serverStopped(FusekiServer) -- call after
server.stop
, but only if a clean shutdown happens. Servers may simply exit without a shutdown phase. The JVM may exit or be killed without clean shutdown. Modules must not rely on a call toserverStopped
happening.
-
Method Summary
Modifier and TypeMethodDescriptiondefault void
configDataAccessPoint
(org.apache.jena.fuseki.server.DataAccessPoint dap, org.apache.jena.rdf.model.Model configModel) This method is called for eachDataAccessPoint
by the default implementation ofFusekiBuildCycle.configured(org.apache.jena.fuseki.main.FusekiServer.Builder, org.apache.jena.fuseki.server.DataAccessPointRegistry, org.apache.jena.rdf.model.Model)
after the new servers DataAccessPointRegistry has been built.default void
configured
(FusekiServer.Builder serverBuilder, org.apache.jena.fuseki.server.DataAccessPointRegistry dapRegistry, org.apache.jena.rdf.model.Model configModel) Called after theDataAccessPointRegistry
has been built.name()
Display name to identify this module.default void
prepare
(FusekiServer.Builder serverBuilder, Set<String> datasetNames, org.apache.jena.rdf.model.Model configModel) Called at the start of "build" step.default void
server
(FusekiServer server) Called when the server is built at the point where it is returned from theFuseki server builder
.default void
serverAfterStarting
(FusekiServer server) Server started - called just after server.start happens, and before server .start() returns to the application.default void
serverBeforeStarting
(FusekiServer server) Server starting - called just before server.start happens.default boolean
serverConfirmReload
(FusekiServer server) Confirm or reject a request to reload.default void
serverReload
(FusekiServer server) A running server has been asked to reload its configuration.default void
serverStopped
(FusekiServer server) Server stopping.
-
Method Details
-
name
String name()Description copied from interface:FusekiBuildCycle
Display name to identify this module.- Specified by:
name
in interfaceFusekiBuildCycle
-
prepare
default void prepare(FusekiServer.Builder serverBuilder, Set<String> datasetNames, org.apache.jena.rdf.model.Model configModel) Description copied from interface:FusekiBuildCycle
Called at the start of "build" step. The builder has been set according to the configuration of API calls and parsing configuration files. No build actions have been carried out yet. The module can make further FusekiServer.FusekiServer.Builder
calls. The "configModel" parameter is set if a configuration file was used otherwise it is null.This is the main point for customization of server.
It can add and modify the data services being built, and also add servlets and servlet filters.
- Specified by:
prepare
in interfaceFusekiBuildCycle
- Parameters:
serverBuilder
- The FusekiServer.BuilderdatasetNames
- The names of DataServices configured by API calls and configuration file.
-
configured
default void configured(FusekiServer.Builder serverBuilder, org.apache.jena.fuseki.server.DataAccessPointRegistry dapRegistry, org.apache.jena.rdf.model.Model configModel) Description copied from interface:FusekiBuildCycle
Called after theDataAccessPointRegistry
has been built.The default implementation is to call
FusekiBuildCycle.configDataAccessPoint(DataAccessPoint, Model)
for eachDataAccessPoint
.dapRegistry.accessPoints().forEach(accessPoint->configDataAccessPoint(accessPoint, configModel));
- Specified by:
configured
in interfaceFusekiBuildCycle
-
configDataAccessPoint
default void configDataAccessPoint(org.apache.jena.fuseki.server.DataAccessPoint dap, org.apache.jena.rdf.model.Model configModel) This method is called for eachDataAccessPoint
by the default implementation ofFusekiBuildCycle.configured(org.apache.jena.fuseki.main.FusekiServer.Builder, org.apache.jena.fuseki.server.DataAccessPointRegistry, org.apache.jena.rdf.model.Model)
after the new servers DataAccessPointRegistry has been built.- Specified by:
configDataAccessPoint
in interfaceFusekiBuildCycle
-
server
Called when the server is built at the point where it is returned from theFuseki server builder
. The server has not yet been started.- Specified by:
server
in interfaceFusekiBuildCycle
-
serverConfirmReload
Confirm or reject a request to reload.Not all servers or server modules may be able to reload. This is reload of a live server that continued to execute while reload happens and which completes all outstanding requests at the time of the reload request.
Return true if reload is possible. If all modules return true the reload continues and
FusekiBuildCycle.serverReload(org.apache.jena.fuseki.main.FusekiServer)
will be called. If any module returns false, the reload is not performed.- Specified by:
serverConfirmReload
in interfaceFusekiBuildCycle
-
serverReload
A running server has been asked to reload its configuration.Certain server feature will not change.
- http and https connectiosn are preserved.
- Port number
- JVM process
- Specified by:
serverReload
in interfaceFusekiBuildCycle
-
serverBeforeStarting
Server starting - called just before server.start happens.- Specified by:
serverBeforeStarting
in interfaceFusekiStartStop
-
serverAfterStarting
Server started - called just after server.start happens, and before server .start() returns to the application.- Specified by:
serverAfterStarting
in interfaceFusekiStartStop
-
serverStopped
Server stopping. Do not rely on this called; do not rely on this to clear up external resources. Usually there is no stop phase and the JVM just exits or is killed externally.- Specified by:
serverStopped
in interfaceFusekiStartStop
-