jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "A. Soroka (JIRA)" <>
Subject [jira] [Commented] (JENA-1597) Split module jena-fuseki-core into the engine and separate webapp.
Date Sat, 01 Sep 2018 22:47:00 GMT


A. Soroka commented on JENA-1597:

So the idea is that {{jena-fuseki-engine}} would, so to speak, accept datasets and support
HTTP, whereas {{jena-fuseki-webapp}} would add to that configuration and management to decide
_which_ datasets are being served?


My one point of confusion is how the admin API/UI will distribute out. It's got to understand
the specifics of different backends to create datasets, doesn't it? Or do we have some service
by which dataset implementations can advertise their availability?

> Split module jena-fuseki-core into the engine and separate webapp.
> ------------------------------------------------------------------
>                 Key: JENA-1597
>                 URL:
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Fuseki
>    Affects Versions: Jena 3.8.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Major
> The module jena-fuseki-core has both the core of Fuseki (data registries, service servlets,
the servlet filter) and the webapp code needed for the full server with UI.
> The embedded Fuseki does not need the webapp.
> Separating the two aspects into separate modules is cleaner and avoids the risk of webapp
assumptions leaking into the non-webapp embedded server.
> The key difference is that the embedded/base server makes no assumptions about disk,
it is given datasets to manage, where as the webapp full/UI server has an on-disk configuration
and database area.

This message was sent by Atlassian JIRA

View raw message