]
Geoffrey De Smet updated JBRULES-2293:
--------------------------------------
Fix Version/s: 5.3.0.Beta1
(was: 5.2.0.Final)
Classpath resources being scanned by ResourceChangeScanner could
cause improper resource removal
------------------------------------------------------------------------------------------------
Key: JBRULES-2293
URL:
https://issues.jboss.org/browse/JBRULES-2293
Project: Drools
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: drools-core
Affects Versions: 5.0.1.FINAL
Environment: Windows XP
Java 5
Running in Oracle OC4J 10.1.3.2
Reporter: Steve Ronderos
Assignee: Esteban Aliverti
Fix For: 5.3.0.Beta1
Attachments: fix_for_classpath_resources.patch
I encountered an issue today with my KnowledgeAgent removing resources from its RuleBase
shortly after creating it. I have the ResourceChangeScanner running in my application.
I tracked the issue back to the scan() method in ResourceChangeScannerImpl. It appears
that the method is trying to identify resources that are no longer available and remove
them from both the RuleBase and future scans. To do this it is checking lastModified on
the resource and on a result of 0 removing the resource. The resources that I configured
in my change-set definitely still exist, but due to URL handler implementation provided by
my classloader, getLastModified always returns 0. (The resource I'm retrieving is
coming from a jar that is in my application's classpath and the URL handler
implementation is oracle.classloader.SharedCodeSourceURL)
Full Email Group trail:
http://www.nabble.com/Issue-with-ResourceChangeScanner-td25792358.html
Michael recommends to never scan classpath resources.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: