[
https://issues.apache.org/jira/browse/JENA-1597?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16607680#comment-16607680
]
Andy Seaborne commented on JENA-1597:
-------------------------------------
I am wondering if two modules {{jena-fuseki-embedded}} and
{{jena-fuseki-basic}} is worth it. I can't see how both would grow. Any future
work like different UI, would go into one or the other.
If so,
{noformat}
jena-fuseki-embedded + jena-fuseki-basic -> jena-fuseki-main
jena-fuseki-server : shading for jena-fuseki-main (+ jena-fuseki-access)
{noformat}
> 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
>
> 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)
