from drools documentation:
Sequential mode can only be used with a StatefulSession and is off by
default. To turn on either set the RuleBaseConfiguration.setSequentail to
true or set the rulebase.conf property drools.sequential to true.
when you use it:
*java.lang.RuntimeException*: Cannot
Michael,
this was Marks reply to me:
...
Thats a mistake, I'll correct it now. If you try it sequential mode
blows up the engine in statefulsession.
Mark
ekke wrote:
in the docs I read:
2.5.6 ... StatelessSession supports sequential mode...
2.5.10 ... Sequential mode can only be used with a
Does the iterator returned by WorkingMemory.iterator support remove()?
I checked the javadoc and the Drools manual, but may have missed it.
Please answer and augment documentation.
- Godmar
___
rules-users mailing list
rules-users@lists.jboss.org
Wouldn't the best approach be to get the FactHandles iterator and retact
them from working memory rather than removing them through the iterator?
Iterator itr = wm.iterateFactHandles();
While(itr.next()) {
FactHandle h = itr.next();
wm.retract(h);
}
This would ensure truth
Godmar Back wrote:
Does the iterator returned by WorkingMemory.iterator support remove()?
I checked the javadoc and the Drools manual, but may have missed it.
If you try it you'll get an exception thrown UnsupportedOperationException
Anstis, Michael (M.) wrote:
Wouldn't the best approach be to get the FactHandles iterator and retact
them from working memory rather than removing them through the iterator?
Iterator itr = wm.iterateFactHandles();
While(itr.next()) {
FactHandle h = itr.next();
wm.retract(h);
}
If you think this is a bug open a jira with a self contained test
showing the problem
Mark
[EMAIL PROTECTED] wrote:
Subject:
RE: rules-users Digest, Vol 11, Issue 35
From:
[EMAIL PROTECTED]
Date:
Fri, 5 Oct 2007
Excuse me if this would be best posted to the developer list...
...but let me undertstand: The Fact table maintained for a WorkingMemory is
not thread safe(?); however WorkingMemories are thread safe - suggesting
Shadow Facts and (excuse my vague terminolgy) Node Memories are the thread
safe
Does MVEL provide a syntax to check for membership in a map's key or
value sets, e.g., something like:
map.keys contains X
map containsKey X?
- Godmar
___
rules-users mailing list
rules-users@lists.jboss.org
The WM is thread safe, on all insert/update/delete we apply a lock
making sure that not more than one operation can happen. However we do
not apply this lock when the iteraters are used externally via users -
so while iterating any working memroy actions should be avoided. For the
minute I
Hi,
I have couple of questions
1) I want to validate a Object and based upon certain condition set the flag
and that flag available in my working memory context so that all the rules will
execute based on the value of this flag. Is there any way to set the Global
variable in working memory
11 matches
Mail list logo
