[
https://issues.apache.org/jira/browse/JENA-2282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17493603#comment-17493603
]
Bruno P. Kinoshita commented on JENA-2282:
------------------------------------------
As far as I know these settings are read from the assembler to create from a
config. Then in Fuseki you can look at the servlets to see how it's loaded,
e.g.
[https://github.com/apache/jena/blob/31dc0d328c4858401e5d3fa99702c97eba0383a0/jena-fuseki2/jena-fuseki-webapp/src/main/java/org/apache/jena/fuseki/webapp/FusekiWebapp.java#L218]
Every time you start the Tomcat server, or Jetty container, they will start the
application listeners, that will reload the configuration from disk (or from
command line arguments). But as far as I know these routines need to read
assemblers from disk first, to then know where to load the datasets from, what
settings these are using, etc.
> Fuseki2 Query Store
> -------------------
>
> Key: JENA-2282
> URL: https://issues.apache.org/jira/browse/JENA-2282
> Project: Apache Jena
> Issue Type: Wish
> Components: Fuseki UI
> Affects Versions: Jena 4.4.0
> Reporter: Nicholas
> Priority: Minor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> Many triplestore applications have a way to store SPARQL queries. These sorts
> of application parts are really useful: you can keep coming back to useful
> queries. If the queries can be named, then you can build up a query library.
> Not hard to make and super useful. Unless there is already an extension for
> this or plans for such, I'm happy to (have my staff) give this a go!
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
