jena-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Andy Seaborne (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JENA-1597) Split module jena-fuseki-core into the engine and separate webapp.
Date Fri, 21 Sep 2018 10:19:00 GMT

     [ https://issues.apache.org/jira/browse/JENA-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Andy Seaborne resolved JENA-1597.
---------------------------------
       Resolution: Fixed
    Fix Version/s: Jena 3.9.0

> Split module jena-fuseki-core into the engine and separate webapp.
> ------------------------------------------------------------------
>
>                 Key: JENA-1597
>                 URL: https://issues.apache.org/jira/browse/JENA-1597
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Fuseki
>    Affects Versions: Jena 3.8.0
>            Reporter: Andy Seaborne
>            Assignee: Andy Seaborne
>            Priority: Major
>             Fix For: Jena 3.9.0
>
>
> 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
(v7.6.3#76005)

Mime
View raw message