[
https://issues.apache.org/jira/browse/JENA-201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13259705#comment-13259705
]
Rob Vesse commented on JENA-201:
--------------------------------
So while I have not made further progress on this I think I now see how to
proceed with this though I don't think I have time to work on this currently.
The main problem as previously discussed is keeping dynamic configuration while
moving to a container agnostic WAR which on the face of it seems rather awkward
but I believe this is doable. I now believe that the way to this is by
utilizing a ServletContextListener
(http://docs.oracle.com/javaee/6/api/javax/servlet/ServletContextListener.html)
- this is a part of the Java Servlets API and is easily registered in a web.xml
file like so:
<listener>
<listener-class>org.apache.jena.fuseki.FusekiContextListener</listener-class>
</listener>
Then the contextInitialized() method can be used to read the configuration file
(which will have to be located at a path within the web app i.e. people will
need to deploy the WAR and then go in and edit the config appropriately prior
to running it) and wire up servlets and filters appropriately since it has
access to the servlet context and can call all the addServlet(), addFilter()
methods etc. as necessary
> 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
