[
http://jira.jboss.com/jira/browse/JBRULES-1104?page=comments#action_12373629 ]
Mark Proctor commented on JBRULES-1104:
---------------------------------------
The main things it does is create an ObjectTypeNode for an inserted object, if one does
not exist for it. When a new ObjectTypenode is added the updateSink now just iterates the
ObjectTypeConf (only exists for inserted conrete types) and pushes through the data from
any matching ObjectTypeNodes - it also resets the cache on just those. So it no longer
iterates the entire working memory and it selectively resets the cache.
Inserted internal Objects (like InitialFactImpl) are lost if no
matching ObjectTypeNodes
-----------------------------------------------------------------------------------------
Key: JBRULES-1104
URL:
http://jira.jboss.com/jira/browse/JBRULES-1104
Project: JBoss Rules
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.GA
Reporter: Mark Proctor
Assigned To: Mark Proctor
Fix For: 4.0.1
We do not remember objects that have no matching ObjectTypeNodes. Instead we should keep
a LinkedList of Ojects that do not have all their interfaces and superclasses matched by
ObjectTypeNodes. This can be checked by the ObjectTypeConf which can cache the total
number of interfaces and superclasses and compare the number against the ObjectTypeNode
cache.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira