You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Andy Seaborne (JIRA)" <ji...@apache.org> on 2013/08/25 19:36:52 UTC

[jira] [Comment Edited] (JENA-201) Deliver Fuseki as a WAR file.

    [ https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13749701#comment-13749701 ] 

Andy Seaborne edited comment on JENA-201 at 8/25/13 5:35 PM:
-------------------------------------------------------------

Prototype of a WAR-deployed Fuseki.
Uses file area /usr/share/fuseki.

This is builds a single war file that looks in /usr/share/fuseki/config-fuseki.ttl for a Fuseki configuration file.  It uses a universal dispatch servlet.  HTML pages are currently not supported.

Much of the FusekiServlet is adapting the existing universal dispatch servlet (SPARQL_UberServlet)
to work with servlet contexts (named webapps).

Limited testing deploying in Tomcat6 and in-memory datasets.

Ideally, the Fuseki build structure would be split into servlets (the core engine, Jetty independent), build for the standalone server and a build for the WAR version.

Use of the WAR version and a large TDB database may not do the web container (tomcat) much good because of TDB's memory needs.  A standalone server isolates this.

                
      was (Author: andy.seaborne):
    Prototype of a WAR-deployed Fuseki.
Uses file area /usr/share/fuseki.
                  
> 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
>              Labels: gsoc2013, mentor
>         Attachments: fuseki-war-proto.zip, GruppoImola_fuseki_war_src.rar
>
>


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira