Well this does not quite work.
Whilst the knowledgebase is rebuilt when changes are detected, requests to
the drools-server are not firing the rules as expected and a test fact is
being returned unmodified.
If new-instance is set to false, then merging of the rules causes errors.
Any thoughts?
Ross H wrote:
There have been previous posts on this problem:
http://drools-java-rules-engine.46999.n3.nabble.com/Starting-resource-cha...
but I was unable to find a resolution, or issue in Jira.
Looking at the code in 5.1.1 (and trunk), I could not find where the
polling and notifier services are started. To overcome the problem I have
modified the following:
drools-spring-1.0.0.xsd (added a start attribute to
resource-change-scanner)
xsd:attribute name="start" use="optional"
type="xsd:boolean"
ResourceChangeScannerBeanFactory (started service in afterPropertiesSet())
if (isStart()) {
ResourceFactory.getResourceChangeNotifierService().start();
ResourceFactory.getResourceChangeScannerService().start();
}
ResourceChangeScannerDefinitionParser (added start attribute)
factory.addPropertyValue( START,
element.getAttribute( START ) );
It seems to be working quite nicely.
Just wondering if this is the right way to go about it, or whether there
is a better method.
Regards RossH
--
View this message in context:
http://drools-java-rules-engine.46999.n3.nabble.com/drools-server-resourc...
Sent from the Drools - User mailing list archive at
Nabble.com.