XStream can instantiate classes that 1) do not implement serialiseable and 2) do not have a default constructor. Here is now Sun14ReflectionProvider http://svn.xstream.codehaus.org/browse/xstream/trunk/xstream/src/java/com... It may not work on all VMs, but we could have it as a pluggeable strategy, would help solve a lot of use cases :) Mark

Mark, This is great and surelly a relief to several users! Really nice! []s Edson Mark Proctor wrote: -- Edson Tirelli Software Engineer - JBoss Rules Core Developer Office: +55 11 3124-6000 Mobile: +55 11 9218-4151 JBoss, a division of Red Hat @ www.jboss.com

Steven, Hiya, how is that going? I think someone at JBoss was hoping to help you out with it, has mic given you the details? I haven't moved templates across to MVEL yet, but yes eventually that makes sense. However don't go out of your way, more important you get it finished first :) Really hoping that it will make our end of Q1 release :) Mark Steven Williams wrote:

Mark, Nice treasure you found. I will do some research to be able to use the same for shadow facts when the classes are available in the JVM.. []s Edson Mark Proctor wrote: -- Edson Tirelli Software Engineer - JBoss Rules Core Developer Office: +55 11 3124-6000 Mobile: +55 11 9218-4151 JBoss, a division of Red Hat @ www.jboss.com

If we know that facts will only have their values altered in the consequence, during the execution of the working memory, we can dispense with shadow facts - instead we can alter the "setter" to do a retract and assert. What was the overhead of shadow facts in the end, about 10%? so this should help the benchmarks. This should also help with problems such as marcos's, where he is dealing with a million and upwards facts. Mark

The truth maintenance system, and thus logical assertions, are now optional (default is on). This can be configured in the RuleBaseConfiguration. Mark

you could go with the option of having a parameter for the assert. if the user knows they absolutely don't want shadow and plan to assert 1million facts, they can assert without shadow. otherwise they can call the default assert. jamocha's assert has 4 parameters assertObject(Object data, String template, boolean statc, boolean shadow) of course if someone uses JSR94, they won't be able to do anything beyond the stupid API peter On 2/10/07, Mark Proctor <mproctor(a)codehaus.org&gt; wrote:

yeah, the fix to the NOT makes a difference. fixing the propogation speeded it up quite a bit. Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp. d:\>e: E:\>cd drools_benchmark E:\drools_benchmark>dir Volume in drive E is web Volume Serial Number is E4F3-C7AE Directory of E:\drools_benchmark 02/10/2007 04:35 PM <DIR> . 02/10/2007 04:35 PM <DIR> .. 02/10/2007 08:32 AM 9,312 build.xml 02/10/2007 11:32 AM 5,809 hs_err_pid1400.log 02/10/2007 04:35 PM 5,807 hs_err_pid1940.log 02/10/2007 11:33 AM 5,806 hs_err_pid3380.log 02/10/2007 11:45 PM <DIR> lib 02/10/2007 08:32 AM <DIR> src 02/10/2007 08:35 AM <DIR> target 4 File(s) 26,734 bytes 5 Dir(s) 4,381,552,640 bytes free E:\drools_benchmark>e:\ant\bin\ant Buildfile: build.xml help: [echo] usage: [echo] run-drools-waltz50 [echo] run-drools-waltz50-withprints [echo] run-drools-manners128 [echo] run-drools-manners128-withprints [echo] run-drools-manners128-noLeftIndexing [echo] run-jess-waltz50 [echo] run-jess-waltz50-withprints [echo] run-jess-manners128 [echo] run-jess-manners128-withprints [echo] run-jess-javabean-manners128 [echo] run-jess-javabean-manners128-withprints BUILD SUCCESSFUL Total time: 0 seconds E:\drools_benchmark>e:\ant\bin\ant run-drools-manners128-noLeftIndexing Buildfile: build.xml run-drools-manners128-noLeftIndexing: [java] Using [java] engine: drools [java] rule file: manners.drl [java] data file: manners128.dat [java] All Done [java] RESULTS: [java] - Rules parsing time : 6219 ms - Memory used: + 30201 Kb [java] - Assertion time : 172 ms - Memory used: + 931 Kb [java] - Rules firing time : 11829 ms - Memory used: + -12874 Kb [java] ---------------------------------------------------------------- [java] - Total time : 18220 ms - Total memory: + 18258 Kb [java] - GC Run time : 78 ms - Mem after GC: + 4175 Kb [java] Total Created: 0 [java] -------------------- [java] Total Cancelled: 0 [java] -------------------- [java] Total Fired: 0 [java] -------------------- [java] Using [java] engine: drools [java] rule file: manners.drl [java] data file: manners128.dat [java] All Done [java] RESULTS: [java] - Rules parsing time : 1839 ms - Memory used: + 14921 Kb [java] - Assertion time : 94 ms - Memory used: + 0 Kb [java] - Rules firing time : 11191 ms - Memory used: + 34074 Kb [java] ---------------------------------------------------------------- [java] - Total time : 13124 ms - Total memory: + 48995 Kb [java] - GC Run time : 109 ms - Mem after GC: + 3047 Kb [java] Total Created: 0 [java] -------------------- [java] Total Cancelled: 0 [java] -------------------- [java] Total Fired: 0 [java] -------------------- [java] Using [java] engine: drools [java] rule file: manners.drl [java] data file: manners128.dat [java] All Done [java] RESULTS: [java] - Rules parsing time : 1215 ms - Memory used: + 14915 Kb [java] - Assertion time : 16 ms - Memory used: + 0 Kb [java] - Rules firing time : 11035 ms - Memory used: + 34113 Kb [java] ---------------------------------------------------------------- [java] - Total time : 12266 ms - Total memory: + 49029 Kb [java] - GC Run time : 109 ms - Mem after GC: + 3046 Kb [java] Total Created: 0 [java] -------------------- [java] Total Cancelled: 0 [java] -------------------- [java] Total Fired: 0 [java] -------------------- [java] Using [java] engine: drools [java] rule file: manners.drl [java] data file: manners128.dat [java] All Done [java] RESULTS: [java] - Rules parsing time : 1543 ms - Memory used: + 14915 Kb [java] - Assertion time : 16 ms - Memory used: + 0 Kb [java] - Rules firing time : 11019 ms - Memory used: + 34112 Kb [java] ---------------------------------------------------------------- [java] - Total time : 12578 ms - Total memory: + 49028 Kb [java] - GC Run time : 140 ms - Mem after GC: + -8976 Kb [java] Total Created: 0 [java] -------------------- [java] Total Cancelled: 0 [java] -------------------- [java] Total Fired: 0 [java] -------------------- [java] Using [java] engine: drools [java] rule file: manners.drl [java] data file: manners128.dat [java] All Done [java] RESULTS: [java] - Rules parsing time : 1419 ms - Memory used: + 14915 Kb [java] - Assertion time : 15 ms - Memory used: + 0 Kb [java] - Rules firing time : 11160 ms - Memory used: + 34112 Kb [java] ---------------------------------------------------------------- [java] - Total time : 12594 ms - Total memory: + 49027 Kb [java] - GC Run time : 109 ms - Mem after GC: + 3045 Kb [java] Total Created: 0 [java] -------------------- [java] Total Cancelled: 0 [java] -------------------- [java] Total Fired: 0 [java] -------------------- [java] Using [java] engine: drools [java] rule file: manners.drl [java] data file: manners128.dat [java] All Done [java] RESULTS: [java] - Rules parsing time : 1044 ms - Memory used: + 14915 Kb [java] - Assertion time : 31 ms - Memory used: + 0 Kb [java] - Rules firing time : 11129 ms - Memory used: + 34114 Kb [java] ---------------------------------------------------------------- [java] - Total time : 12204 ms - Total memory: + 49029 Kb [java] - GC Run time : 109 ms - Mem after GC: + 3046 Kb [java] Total Created: 0 [java] -------------------- [java] Total Cancelled: 0 [java] -------------------- [java] Total Fired: 0 [java] -------------------- [java] Using [java] engine: drools [java] rule file: manners.drl [java] data file: manners128.dat [java] All Done [java] RESULTS: [java] - Rules parsing time : 1200 ms - Memory used: + 14915 Kb [java] - Assertion time : 15 ms - Memory used: + 0 Kb [java] - Rules firing time : 11082 ms - Memory used: + 34112 Kb [java] ---------------------------------------------------------------- [java] - Total time : 12297 ms - Total memory: + 49028 Kb [java] - GC Run time : 109 ms - Mem after GC: + 3045 Kb [java] Total Created: 0 [java] -------------------- [java] Total Cancelled: 0 [java] -------------------- [java] Total Fired: 0 [java] -------------------- [java] Using [java] engine: drools [java] rule file: manners.drl [java] data file: manners128.dat [java] All Done [java] RESULTS: [java] - Rules parsing time : 702 ms - Memory used: + 14915 Kb [java] - Assertion time : 0 ms - Memory used: + 0 Kb [java] - Rules firing time : 11050 ms - Memory used: + 34112 Kb [java] ---------------------------------------------------------------- [java] - Total time : 11752 ms - Total memory: + 49027 Kb [java] - GC Run time : 125 ms - Mem after GC: + -12700 Kb [java] Total Created: 0 [java] -------------------- [java] Total Cancelled: 0 [java] -------------------- [java] Total Fired: 0 [java] -------------------- [java] Using [java] engine: drools [java] rule file: manners.drl [java] data file: manners128.dat [java] All Done [java] RESULTS: [java] - Rules parsing time : 421 ms - Memory used: + 14915 Kb [java] - Assertion time : 0 ms - Memory used: + 0 Kb [java] - Rules firing time : 11144 ms - Memory used: + 34114 Kb [java] ---------------------------------------------------------------- [java] - Total time : 11565 ms - Total memory: + 49029 Kb [java] - GC Run time : 124 ms - Mem after GC: + 3046 Kb [java] Total Created: 0 [java] -------------------- [java] Total Cancelled: 0 [java] -------------------- [java] Total Fired: 0 [java] -------------------- [java] Using [java] engine: drools [java] rule file: manners.drl [java] data file: manners128.dat [java] All Done [java] RESULTS: [java] - Rules parsing time : 530 ms - Memory used: + 14915 Kb [java] - Assertion time : 0 ms - Memory used: + 0 Kb [java] - Rules firing time : 11035 ms - Memory used: + 34112 Kb [java] ---------------------------------------------------------------- [java] - Total time : 11565 ms - Total memory: + 49028 Kb [java] - GC Run time : 125 ms - Mem after GC: + 3045 Kb [java] Total Created: 0 [java] -------------------- [java] Total Cancelled: 0 [java] -------------------- [java] Total Fired: 0 [java] -------------------- BUILD SUCCESSFUL Total time: 2 minutes 10 seconds E:\drools_benchmark> On 2/10/07, Mark Proctor <mproctor(a)codehaus.org&gt; wrote:

I guess its more to do with the drl. We currently have: count.setValue(.....); modify( count ); now I can do a regexp that changes count.setValue(....); to retract( count ); count.setValue(...); assert( account ); But then what happens if the user used modify. One of the advantages of using modify(....) is you control when the progation occurs, ideal if you are updating lots of values on the same object. And ofcourse i have the backward compatability issue. Mark Peter Lin wrote:

I think it will be hard. My preference is to change the drl to do a retract+assert on a modify, that way we don't need shadow facts - as long as they keep the modifies strictly inside the drl - which I think is fair. Mark Edson Tirelli wrote:

Mark, Follows the list of main features added to core/compiler I was able to get from JIRA. Do you want me to ellabora on each item or the JIRA is enough and we focus on documentation? I think it would be good to start a wiki page on migration from 3.0.x to 3.2. What do you think? []s Edson LANGUAGE IMPROVEMENTS * New conditional elements: from, collect, accumulate, forall http://jira.jboss.com/jira/browse/JBRULES-486 http://jira.jboss.com/jira/browse/JBRULES-337 http://jira.jboss.com/jira/browse/JBRULES-341 http://jira.jboss.com/jira/browse/JBRULES-218 * Full support to FOL: nesting of elements now complete http://jira.jboss.com/jira/browse/JBRULES-218 * Support to connective constraints: http://jira.jboss.com/jira/browse/JBRULES-216 * Parser improvements: - Keyword conflicts resolved http://jira.jboss.com/jira/browse/JBRULES-214 - Better support to line breaks http://jira.jboss.com/jira/browse/JBRULES-269 - Support to escaped characters inside strings http://jira.jboss.com/jira/browse/JBRULES-519 * Primitive type support: no more autoboxing/unboxing http://jira.jboss.com/jira/browse/JBRULES-527 * Support to Templates: http://jira.jboss.com/jira/browse/JBRULES-330 * Support to additional predicate syntax: http://jira.jboss.com/jira/browse/JBRULES-556 CORE IMPROVEMENTS: * Shadow facts: http://jira.jboss.com/jira/browse/JBRULES-44 * Support to constraints between fields of the same object: http://jira.jboss.com/jira/browse/JBRULES-515 * Performance improvements http://jira.jboss.com/jira/browse/JBRULES-484 http://jira.jboss.com/jira/browse/JBRULES-498 http://jira.jboss.com/jira/browse/JBRULES-526 * Specialized "exists" node for performance: http://jira.jboss.com/jira/browse/JBRULES-547 -- Edson Tirelli Software Engineer - JBoss Rules Core Developer Office: +55 11 3124-6000 Mobile: +55 11 9218-4151 JBoss, a division of Red Hat @ www.jboss.com Mark Proctor wrote: -- Edson Tirelli Software Engineer - JBoss Rules Core Developer Office: +55 11 3124-6000 Mobile: +55 11 9218-4151 JBoss, a division of Red Hat @ www.jboss.com

Here's a small text that describes the most important improvements compared to 3.0.x: The IDE now supports debugging rules: breakpoints can be added in drl files for rule right-hand side (consequences) and inside functions. Whenever a rule breakpoint is encounter during debugging, the corresponding rule is shown, and you can step through. Rule debugging is completely integrated with standard java debugging, so both can be used at the same time. A new Rules view allows you to get a quick overview of all the rules, functions, queries, functions and globals in your workspace. You can also quickly navigate to them by double clicking the selected element. Support for the new language features (like from, collect, accumulate) has also been included, and the IDE has been updated to support all other changes to the core. And continuously improving and fine-tuning other functionality, like adding filtering to the outline (and rules) view, (configurable) caching of parser results, etc. Kris ----- Original Message ----- From: "Mark Proctor" <mproctor(a)codehaus.org&gt; To: "Rules Dev List" <rules-dev(a)lists.jboss.org&gt; Sent: Sunday, February 11, 2007 3:52 PM Subject: [rules-dev] M1 Disclaimer: http://www.kuleuven.be/cwis/email_disclaimer.htm

After a long walk and thinking about shadow facts I think the only way forward is to remove modify(....) from drl consequences. Modify will exist external via the WorkingMemory interface, but shadow facts must be turned on for that class for it to work. To allow a series of setters for a single propagation to be done in a drl we must move to one of the following the following syntaxes: person(name = mark, age = 31) person.setValues(name = mark, age = 31) person.(name = mark, age = 31) Or some variation of the above, we will then use regular expression on known declarations to turn person(name = mark, age = 31) into : retract( person, MODIFY ); person.setName( mark ); person.setAge( 31 ); assert( person, MODIFY ); The MODIFYis a keyword to indicate that the propagation is a MODIFICATION PropertChangeListeners shouldn't have an issue as we can dictate that they also do a retract and assert, before and after the setting of the value. Hmm if you are in a consequence and modify a field on a propertychangelistener fact, you'll need to detect whether the regexp or the fact handles the retract + assert. I still have plans to "weave" facts to allow them to seamlessly handle modifies, I had a mock up implementation for this (uncommitted) and lost it when I sent my laptop back to dell, forget to back it up :( Still shouldn't take long to remake that. Mark Proctor wrote: