I am looking to implement a system that has as facts "events" that happen
randomly.
How is the best way to implement a "garbage collection" mechanism that if the
number of "events" in the working memory reaches a limit value will retract the
oldest event/s.
Thanks
--zoly
_
Edson Tirelli wrote:
Forgot to say that we are doing an effort to completely remove
shadow proxies in the next major version.
Yes i have a branch now that does not need shadow proxies at all. We
will probably recommend an AOP approach for those that need integrity
protection in a multi-th
No, mailing list is good for initial assessment and talkings, but JIRAs
are the place for tickets... if it is not in JIRA it may be forgotten.
Regarding tickets, you are welcome to help knocking them out if you want
to... :) just pop up in the IRC and we can get you up to speed.
[]s
E
That would be good. I was a bit concerned about Mark's comment
implying that you deal with the mailing list first, then with JIRAs.
I'm finding 4.0.4 very difficult to work with, I'm practically
encountering parsing/dialect issues constantly, making it very
difficult to achieve my actual goal.
-
As a general comment, the examples for which I find Drools failing are
not the actual examples for which my application is failing. It's just
the smallest test case I was able to eliminate.
I'm now a bit concerned about your comment that Maps and Collections
aren't well-defined as Facts. I am plan
Consider this test:
---
package tests;
import java.lang.reflect.Method;
dialect "mvel"
rule "Rule #1"
when
then
Class clazz = Class.forName("java.lang.Class");
System.out.println("clazz = " + clazz);
Method m = clazz.getDeclaredMethod("forName", new Class [] {
java.lang.String.class
Hi ALL, This is my first project on drools. I am using JBOSS rules 4.0.4 and
wouldlike your help. I want to create a spreadsheet that will compile into drl
file. I can notfigure out how I could create an OR condition in the
spreadsheet. The drlcode I am looking to get finally will look like
Ok, I guess we must hire you as our QA person. :)
Please, keep reporting and opening JIRAs. I'm working on getting as much
as possible fixed.
[]s
Edson
2008/2/19, Godmar Back <[EMAIL PROTECTED]>:
>
> Hi,
>
> here's a simple test for which Drools 4.0.4 w/ MVEL 1.4 loops infinitely:
>
>
Forgot to say that we are doing an effort to completely remove shadow
proxies in the next major version.
2008/2/19, Edson Tirelli <[EMAIL PROTECTED]>:
>
>
>Drools tries to create the ShadowProxy. The reason is that it does not
> know about the implementation... it just knows it is a Map and
Drools tries to create the ShadowProxy. The reason is that it does not
know about the implementation... it just knows it is a Map and as so, it
must be shadowed. Problem is that SingletonMap is either final or does not
have a default constructor.
My recommendation, besides opening a JIRA for
Hehe, my question is because 14 means it was compiled to JDK 1.4... the
actual version is 1.2.21. :)
Well, it seems it is a bug... I see you open several tickets in the
JIRA.. I'm going through some of them... if you didn't opened one for this,
may I ask you please to do it?
Thanks,
> md5sum ../WEB-INF/lib/mvel14-1.2.21.jar
67b9f1dd16b353327a9ef4fe708a8b62 ../WEB-INF/lib/mvel14-1.2.21.jar
(I'm pretty certain this time...)
On Feb 19, 2008 1:41 PM, Edson Tirelli <[EMAIL PROTECTED]> wrote:
>
>Godmar,
>
>Can you please confirm what version of MVEL you are using?
>
>
Godmar,
Can you please confirm what version of MVEL you are using?
Thanks,
Edson
2008/2/19, Godmar Back <[EMAIL PROTECTED]>:
>
> Hi,
>
> with Drools 4.0.4 and MVEL 1.4, simple RHS like this one fail for me:
>
> ---
> package test;
>
> dialect "mvel"
>
> rule "Rule #1"
> when
> th
Hi,
with Drools 4.0.4 and MVEL 1.4, simple RHS like this one fail for me:
---
package test;
dialect "mvel"
rule "Rule #1"
when
then
System.out.println("now computing 1+1...");
Integer two = new Integer(2);
System.out.println(two);
end
---
now computing 1+1...
org.mvel.CompileExcept
Hi,
here's a simple test for which Drools 4.0.4 w/ MVEL 1.4 loops infinitely:
package tests;
import java.util.Map;
import java.io.File;
dialect "mvel"
rule "Rule #1"
when
p : Map (this["path"] matches File.separator);
then
System.out.println("cgi path " + p.path);
end
It app
Hi,
usings Drools 4.0.4 and MVEL 1.4, this simple rule:
---
package test;
import java.util.Collections;
dialect "mvel"
rule "Rule #1"
when
then
insert(Collections.singletonMap("content", "hello"));
end
--
produces:
java.lang.IllegalAccessError: class
org.drools.shadow.java.util.Collections
Christie, Blair wrote:
In the documents this is dicussed briefly:
"). Object models can often have complex relationships and hierarchies
in them - for rules you will want to simplify and flatten the model
where possible, and let the rule engine infer relationships (as it
provides future flex
In the documents this is dicussed briefly:
"). Object models can often have complex relationships and hierarchies
in them - for rules you will want to simplify and flatten the model
where possible, and let the rule engine infer relationships (as it
provides future flexibility."
What does it m
Done in trunk too:
http://jira.jboss.com/jira/browse/JBRULES-1472
[]s
Edson
2008/2/18, Edson Tirelli <[EMAIL PROTECTED]>:
>
>
>This is fixed on 4.0.x branch. I will fix in trunk.
>
>[]s
>Edson
>
> 2008/2/8, Edson Tirelli <[EMAIL PROTECTED]>:
> >
> >
> >Ok, I see the prob
Hi there,
I have got a couple of questions about ruleflows and woking memory.
What does happen each time I modify a fact within a ruleflow node without
calling update(fact)?
What does happen between the node where I
apllied the modifications and the next activation node?
I guess that between on
20 matches
Mail list logo
