The rule binary stuff is cached (in memory) so it should be faster then the older version, but may use more memory. We are looking at a way to keep binaries in eclipse as "derived artifacts" much like class files are, which will both keep it fast, and keep the memory down for people with lots of classes and rules.
Michael,You're good. I switched to a newer Eclipse install for my JBRules 3.1-M1 "eval" and completely forgot to adjust my VM args. Thanks for the reminder.BreeOn Apr 18, 2007, at 8:29 PM, Michael Neale wrote:Bree, also check you are throwing enough memory at eclipse - with lots of rules and code, if eclipse doesn't have enough and the GC has to work overtime, it can really really suck.On 4/17/07, Bree VanOss <breevanoss@gmail.com> wrote:Michael,
I actually like the basic concept of validating decision tables, my issue is that we have FIT tests (in Excel) in a separate source folder in our "rules project". These .xls files are falsely being identified as decision tables with a ton of problems. Validation also seems to take much longer than it does with the 3.0.x branch (like from 30 seconds in 3.0 to to 5 minutes in 3.1 !?!?). Though the two issues may be related.
A common way of dealing with this problem in Eclipse is to allow for ant-like "source path include/exclude" patterns.
i.e. exclude test/**/*.xls
For that matter it would be nice to have the same thing for standard DRL files. The validation of a large rule base can take some time and randomly results in exceptions much of the time. Once I've tested and verified a set of rules I could (optionally) exclude them from validation.
I'll write this all up in the JIRA this evening.
Thanks again,
BreeOn 4/17/07, Michael Neale < michael.neale@gmail.com> wrote:Hi Bree.
Well, thats a new thing Kris threw in - cause people were asking for it. It should only validate ones in the rules project itself - I assume that is what you mean?
If this is a problem for you, could you create a JIRA and state your case? it may be a case of having an optional config dialog to setup where .xls may live and where they dont.
Regards,
Michael.On 4/17/07, Bree VanOss < breevanoss@gmail.com> wrote:Hi,_______________________________________________
I've started looking at the JBoss Rules 3.1-M1 Eclipse plugin to get an idea of how much migration work I have to look forward to.
The first issue I ran into is that it appears the Drools Builder is validating every Excel (.xls) file I have in my source path. Is this a design decision and if so, how can I "hide" non-decision table .xls files from the Drools builder? I've tried excluding them from the Eclipse Source Path using a "source exclusion rule", but that didn't seem to work.
Thanks,
Bree
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users_______________________________________________rules-users mailing list
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users