[
https://issues.apache.org/jira/browse/JENA-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15364338#comment-15364338
]
ASF GitHub Bot commented on JENA-1204:
--------------------------------------
GitHub user paulhoule opened a pull request:
https://github.com/apache/jena/pull/150
[JENA-1204] support for multiple BuiltinRegistry for different rule sets
This patch introduces support for multiple BuiltinRegistry classes
implemented in a simple way which is parallel to the existing architecture.
(i.e. the BuiltinRegistry is a property of the Rules Engine parser, not the
Reasoner)
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/paulhoule/jena master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jena/pull/150.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #150
----
commit 60f4a0a0f22b25e2ed167f3a4625d037c0d82c2c
Author: Paul Houle <p...@ontology2.com>
Date: 2016-07-06T13:56:04Z
[JENA-1204] support for multiple BuiltinRegistry for different rule sets
----
> Independently Configurable BulitinRegistry for Jena Rules Engine
> ----------------------------------------------------------------
>
> Key: JENA-1204
> URL: https://issues.apache.org/jira/browse/JENA-1204
> Project: Apache Jena
> Issue Type: New Feature
> Components: Jena
> Affects Versions: Jena 3.1.1
> Environment: any
> Reporter: Paul Houle
> Labels: rules
> Original Estimate: 48h
> Remaining Estimate: 48h
>
> 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)
