[
https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13751088#comment-13751088
]
Andy Seaborne commented on JENA-201:
------------------------------------
Rob - yes, that'll get to the same functionality as the standalone server (with
caveats).
At the moment, the {{pages/}} area is mounted as the root static content and
reside on disk. When starting the standalone server you can have them
somewhere else, use your own or editted pages, or arrange for no pages.
If included in the WAR file:
* The pages are always available.
* The pages are fixed.
* request routing needs to be page sensitive.
None of theose are entirely desirable. I guess it's framing what the WAR
version is for; whether it is the standalone server but running in Tomcat or
meeting a deployment need for a SPARQL server, where no pages makes sense.
Re: routing: to make the system generic, there is one uber SPARQL servlet to do
all the routing (it's set as {{/\*}}) so web.xml needs to have {{\*.html}},
{{\*.css}}, {{...}} settings. In the standalone server, servlets are
explicitly added for each service of each dataset, as if web.xml has
{{/ds/query -> SPARQL_QueryDataset}}, {{/ds/update -> SPARQL_Update}}, ... .
See also JENA-350 (use of session cookies) and JENA-420 (new UI).
This prototype webapp setup is a pure SPARQL server for programmatic access.
> 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
