[
https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13208576#comment-13208576
]
Jacobus Geluk edited comment on JENA-201 at 2/15/12 4:47 PM:
-------------------------------------------------------------
Andy, I have created a fork of jena-fuseki on github
(https://github.com/jgeluk/jena-fuseki), where I used your main Joseki servlet
as the basis for a similar Fuseki servlet. Called it ConfigServlet
(https://github.com/jgeluk/jena-fuseki/blob/trunk/src/main/java/org/apache/jena/fuseki/server/ConfigServlet.java)
and put it next to the SPARQLServer class since it's kind of the
Servlet-equivalent of that class. It loads the config.ttl but in order to
dynamically create the other Servlets, like is done for Jetty in SPARQLServer,
such as SPARQL_QueryGeneral and SPARQL_REST, I need to implement the Tomcat
specific interface ContainerServlet, which makes it a privileged Servlet. Not
really an elegant solution since it would require an additional parameter in
Context.xml (and make it Tomcat specific).
So I guess the only proper way to do this is to make that dispatcher as you
suggested. I guess it would be similar to what Joseki does then? Any hints?
was (Author: jgeluk):
Andy, I have created a [https://github.com/jgeluk/jena-fuseki|fork of
jena-fuseki on github], where I used your main Joseki servlet as the basis for
a similar Fuseki servlet. Called it
[ConfigServlet|https://github.com/jgeluk/jena-fuseki/blob/trunk/src/main/java/org/apache/jena/fuseki/server/ConfigServlet.java]
and put it next to the SPARQLServer class since it's kind of the
Servlet-equivalent of that class. It loads the config.ttl but in order to
dynamically create the other Servlets, like is done for Jetty in SPARQLServer,
such as SPARQL_QueryGeneral and SPARQL_REST, I need to implement the Tomcat
specific interface ContainerServlet, which makes it a privileged Servlet. Not
really an elegant solution since it would require an additional parameter in
Context.xml (and make it Tomcat specific).
So I guess the only proper way to do this is to make that dispatcher as you
suggested. I guess it would be similar to what Joseki does then? Any hints?
> Deliver Fuseki as a WAR file.
> -----------------------------
>
> Key: JENA-201
> URL: https://issues.apache.org/jira/browse/JENA-201
> Project: 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
