You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Paul Houle (JIRA)" <ji...@apache.org> on 2016/07/05 14:44:11 UTC
[jira] [Created] (JENA-1204) Independently Configurable
BulitinRegistry for Jena Rules Engine
Paul Houle created JENA-1204:
--------------------------------
Summary: Independently Configurable BulitinRegistry for Jena Rules Engine
Key: JENA-1204
URL: https://issues.apache.org/jira/browse/JENA-1204
Project: Apache Jena
Issue Type: Bug
Components: Jena
Affects Versions: Jena 3.1.1
Environment: any
Reporter: Paul Houle
An appealing case for the Jena Rules Engine is to use rules to trigger a set of actions in the rule heads that create side effects in the Java Universe: consider (1) constructing and populating Java data structures in the rule head, and (2) use of the rules engine in a "reactive" scenario where changes in the outside world are inserted into the graph as facts, triggering actions on a distributed system in the heads.
In cases like this, the creation of a new set of built-ins could occur somewhat frequently so efficiency matters here so I don't like the idea of this registered in some central registry so that we can pass in the built-in parameter with the resource to the factory, so the advised method for configuration is to add a setter on the GenericRuleReasoner, The only concern I have is "order-of-operations" involving initialization, etc.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)