Hello, some of our custom operators need to access already inserted facts at runtime. Therefore we extended *org.drools.base.BaseEvaluator*. The provide methods, i. e. *public boolean evaluate(InternalWorkingMemory workingMemory, InternalReadAccessor extractor, Object object, FieldValue value)*, state, amongst others, a parameter "workingMemory" of type *org.drools.common.InternalWorkingMemory*. When calling *workingMemory.getObjects()* we receive a "UnsupportedOperationException". The question is whether it is possible to access facts in a KnwoledgeSession at runtime or not. Alternatively we could provide the objects in question as globals and call workingMemory.getGlobal(), but that seems to me like somewhat bad architecture. Any suggestions are welcome. Many thanks, -Matthias _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users

Exactly! I need to iterate over a bunch of objects/facts in the Working Memory. *Von:* rules-users-bounces(a)lists.jboss.org [mailto: rules-users-bounces(a)lists.jboss.org] *Im Auftrag von *Vincent Legendre *Gesendet:* Freitag, 10. Juni 2011 12:04 *An:* Rules Users List *Betreff:* Re: [rules-users] Custom-Operator - No access to FactHandles? And why not accessing the object itself directly ? Because the evaluation of one object field depends on others objects in WM ? Le 10/06/2011 11:54, Martin, Matthias a écrit : Hello, some of our custom operators need to access already inserted facts at runtime. Therefore we extended *org.drools.base.BaseEvaluator*. The provide methods, i. e. *public boolean evaluate(InternalWorkingMemory workingMemory, InternalReadAccessor extractor, Object object, FieldValue value)*, state, amongst others, a parameter “workingMemory” of type * org.drools.common.InternalWorkingMemory*. When calling *workingMemory.getObjects()* we receive a “UnsupportedOperationException”. The question is whether it is possible to access facts in a KnwoledgeSession at runtime or not. Alternatively we could provide the objects in question as globals and call workingMemory.getGlobal(), but that seems to me like somewhat bad architecture. Any suggestions are welcome. Many thanks, -Matthias _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users -- Vincent LEGENDRE *Consultant Sénior* EURODECISION 9A rue de la Porte de Buc 78000 VERSAILLES Tél. : +33 (0)1 39 07 12 40 Direct : +33 (0)1 39 07 26 16 www.eurodecision.com [image: EURODECISION] <http://www.eurodecision.com/> _______________________________________________ rules-users mailing list rules-users(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/rules-users