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

Andy Seaborne commented on JENA-1728:
-------------------------------------

One step here might be to have Fuseki configuration processing skip broken 
dataset configuration not throw a deep exception and refuse to start up.

Thoughts?


> Fuseki Assembler ignore ja:rulesFrom on Error
> ---------------------------------------------
>
>                 Key: JENA-1728
>                 URL: https://issues.apache.org/jira/browse/JENA-1728
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: Fuseki
>    Affects Versions: Jena 3.12.0
>         Environment: GNU/Linux (Debian)
>            Reporter: tdbrec
>            Priority: Major
>              Labels: Assembly, fuseki2, inference, reasoner, ruleengine
>
> {code:java}
> :dataset a ja:InfModel ;
>     ja:baseModel ..... ;
>     ja:reasoner [
>         ja:reasonerURL <http://jena.hpl.hp.com/2003/GenericRuleReasoner> ;
>         ja:rulesFrom <file:///rules-1> ;
>         ja:rulesFrom <file:///rules-2> ;
>     ] .
> {code}
> If one of the files ja:rulesFrom contain syntax errors, Fuseki stops working. 
> It would be useful to have a way for "loading or ignoring" rules, for example 
> ja:rulesOrIgnoreFrom <...>
> My use case is that I'm accepting inference rules from users, and the only 
> way to update inference rules is by writing them to a file, append a new 
> ja:rulesFrom in the configuration, and reload Fuseki. Even though this 
> process is pretty cumbersome for updating rules, at least it's doable and I'm 
> OK with that. The major stopper is that there isn't a way to validate rules, 
> so when I ask Fuseki to load a broken file it will refuse to work until I fix 
> the file manually.
> A different option could be a new "ja:rulesFromDirectory" that will 
> automatically load all files inside a directory ignoring any file that raise 
> an exception.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to