[
https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13400652#comment-13400652
]
Rob Vesse commented on JENA-201:
--------------------------------
To add to the previous discussion probably the most sensible way of WARifying
Fuseki would be to split the project into two:
- fuseki-core - This would be a WAR project that incorporates all the servlets
and refactors the existing configuration mechanism into a
ServletContextListener. Configurations would be managed by assembler files in
the conf/ directory defaulting to fuseki.ttl - we'd provide a selection of
sample files with different configs that people could easily wire up.
- fuseki-server - This would be a JAR project that would basically embed
Jetty/Tomcat and depend on the fuseki-core project in order to provide a
runnable JAR version of the server as with the existing project
Structuring this way allows for us to continue to provide a runnable JAR to get
people started quickly while allowing for a working WAR that advanced users can
drop into the application server of their choice
> Deliver Fuseki as a WAR file.
> -----------------------------
>
> Key: JENA-201
> URL: https://issues.apache.org/jira/browse/JENA-201
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Reporter: Andy Seaborne
> Priority: Minor
>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
