so that works? It should now, there was a problem with BoundVariables before. On 3/29/06, Mark Proctor <m.proctor <at> bigfoot.com> wrote: > > rule "Cheesery contains stilton" > when > stilton : Cheese( type == "stilton" ) > Cheesery( cheeses contains stilton ) > then > list.add( stilton ); > end >
you could do:
s : String()
eval(s == "foo)
with an expander/DSL, so you have sojmething like
{var} : StringValue({s})=={var} : String() eval({var}.equals({s}))
so it looks like in a rule:
s : StringValue("foo")
but thats not quite ideal, as that is binding a variable still.
Perhaps a more general predicate structure like:
Object(this -> ( /** semantic predicate here */ ) )
or some other shorthand. The key is that "this" tells the predicate to
operate on the Column itself. This may suffer from the same problem of
implicitly binding variables (which is what I am trying to avoid).
Note this is very much 3.1 territory now.
Michael.
On 3/29/06, Greg Barton <greg_barton <at> yahoo.com> wrote:
>
> --- Michael Neale <michael.neale <at> gmail.com> wrote:
(Continue reading)
#3 sounds good. 99% of the time we are not adding/removing rules, so we don't wnat to impact the 99% of the time with what will happen 1% of the time ! On 3/30/06, Edson Tirelli <edson.tirelli <at> auster.com.br> wrote: > > Mark, > > I thought about what we discussed regarding the OTN creation and the > rule adding. My considerations are: > > 1. It is possible to map the class hirarchy in an oriented graph during > fact assertion, and this way, when adding a new rule with new OTNs, we > can iterate only over existing object type nodes that might contain > objects that are "assignable from" the new OTNs. Although: > 1.a. this algorithm is pretty complex and there is an assertion > (runtime) cost associated to it, since every time a fact of a new > unknown concrete class is added to the WM we need to map the class > hirarchy and add it to the graph. > 1.b. there is also a cost associated to the adding of a new OTN (when > adding a rule) since we need to run over the graph updating it to > include the added OTNs > > 2. We can stop supporting class hirarchy, but as I said before, I would > be completelly against it. I use this a lot to avoid writing multiple > rules, one for each possible concrete class, when I can instead simply > write a rule for a superclass or interface. > > 3. We can simply hold all facts asserted in a list inside working > memory, independent of class (as we already do), and when adding a new(Continue reading)
I have added decision tables to Drools 3 and the IDE (just the ability to create one from a template). Of course, this requires that an appropriate editor be available on the users system (such as open office, excel etc). I am interested to know if people think thats a good or bad thing. Ultimately, we want to have a JFace based decision table and tree graphical editor integrated.
Michael, I think is a great thing. Decision tables are widely used in the development process I use in my projects. I was thinking we (at my company) could do that for drools 3, but we are lack of time right now (certifing and testing a new app). Is this new feature available on the ide release? Thank you all guys for this new great drools!. :) Sunday, April 2, 2006, 4:29:09 AM, you wrote: > I have added decision tables to Drools 3 and the IDE (just the ability to > create one from a template). Of course, this requires that an appropriate > editor be available on the users system (such as open office, excel etc). > I am interested to know if people think thats a good or bad thing. > Ultimately, we want to have a JFace based decision table and tree graphical > editor integrated. -------------------------- Felipe Piccolini felipe.piccolini <at> bluesoft.cl
yes it will be in the IDE (its in SVN HEAD now). Decision tables are mostly unchanged for 3, a few necessary changes which I will be documenting this week. I also would like to rethink some of the seperation between the data (rows in spreadsheet) and the rule templates... On 4/3/06, Felipe Piccolini <felipe.piccolini <at> bluesoft.cl> wrote: > > Michael, > > I think is a great thing. Decision tables are widely used in the > development process I use in my projects. I was thinking we (at my > company) could do that for drools 3, but we are lack of time right > now (certifing and testing a new app). Is this new feature available > on the ide release? > > Thank you all guys for this new great drools!. :) > > Sunday, April 2, 2006, 4:29:09 AM, you wrote: > > > I have added decision tables to Drools 3 and the IDE (just the ability > to > > create one from a template). Of course, this requires that an > appropriate > > editor be available on the users system (such as open office, excel > etc). > > > I am interested to know if people think thats a good or bad thing. > > Ultimately, we want to have a JFace based decision table and tree(Continue reading)
Thursday 6th of April - 10.30am for about 2-3 hours. Starbucks 376 Chiswick High Road London W4 5TF Look for the guy wearing a grey JBoss t-shirt. For those asking if I can help on other areas of Drools integration, I'll try my best but I'm not an application server or spring expert - my skills are solely in Drools. Mark Mark Proctor wrote: > So I'm thinking, how does thursday April the 6th sound? at 11am. > > Just to be clear, this will be a very informal chat. Where I will > discuss new features in 3.0, show them on my laptop, help you out on a > few 3.0 issues and talk about your approaches and get feedback for the > future. If its successful I'll try and make it a regular thing. It > will be in a coffee shop, so can't have too many people, there will be > no projector... yada yada yada. > > Mark > Mark Proctor wrote: >> I regularly go into Chiswick, London, to work from Star Bucks. With >> the imminent release, on an experimental basis, I'm willing to give >> free informal training on Drools 3.0 to anyone that buys me a coffee.(Continue reading)
We are now turning our attention to documentation. I imagine you are all at home wondering how you can contribute, I know I would be :) There are a number of ways. The best way is to put it into a jira, so its a task for us to do. You can submit a word, html or text file - we'll cut and paste that across to docbook - ofcourse sending us the section in a zip with images and text in docbook format is best :) you can also put stuff into the wiki and we will work it into the manual. Finally if you are planning to do a lot of documentation, which I imagine you all are, you can get svn contributor access and work directly with the docbook xml there. So if you ask a question here or work something out, that should be in the manual, please send in a contribution. Happy Documenting Mark
I am getting an error when I have something like the following:
rule "test eval"
when
cell1 : Cell(value1 : value != 0)
cell2 : Cell(value2 : value < value1)
eval(true)
then
System.out.println("setting value to " + (value2.intValue() + 1));
cell2.setValue(value2.intValue() + 1);
modify(cell2);
end
where Cell is
public class Cell {
int value = 0;
public Cell2(int value)
{
this.value = value;
}
public int getValue() {
return value;
}
public void setValue(int value) {
this.value = value;
(Continue reading)
Steven,
You have a test method you can give me? I'll stick this in as an
integration test and fix it.
Mark
Steven Williams wrote:
> I am getting an error when I have something like the following:
>
> rule "test eval"
> when
> cell1 : Cell(value1 : value != 0)
> cell2 : Cell(value2 : value < value1)
> eval(true)
> then
> System.out.println("setting value to " + (value2.intValue() + 1));
> cell2.setValue(value2.intValue() + 1);
> modify(cell2);
> end
>
> where Cell is
>
> public class Cell {
>
> int value = 0;
>
> public Cell2(int value)
> {
> this.value = value;
> }
(Continue reading)
RSS Feed30 | |
|---|---|
94 | |
80 | |
85 | |
36 | |
19 | |
37 | |
52 | |
49 | |
13 | |
50 | |
44 | |
32 | |
16 | |
87 | |
123 | |
61 | |
36 | |
66 | |
35 | |
104 | |
73 | |
90 | |
102 | |
120 | |
135 | |
117 | |
93 | |
85 | |
144 | |
92 | |
153 | |
138 | |
122 | |
25 | |
47 | |
87 | |
68 | |
58 | |
40 | |
45 | |
30 | |
46 | |
79 | |
40 | |
38 | |
20 | |
27 | |
26 | |
23 | |
40 | |
62 | |
57 | |
38 | |
47 | |
76 | |
31 | |
49 | |
40 | |
26 | |
27 | |
30 | |
23 | |
14 | |
43 | |
13 | |
44 | |
56 | |
17 | |
54 | |
78 | |
36 | |
92 | |
54 | |
83 | |
106 | |
53 | |
75 | |
66 | |
20 | |
23 | |
130 | |
150 | |
22 | |
42 | |
95 | |
121 | |
46 | |
17 | |
26 | |
17 | |
54 | |
38 | |
29 | |
84 | |
30 | |
63 | |
52 | |
86 | |
50 | |
16 | |
15 | |
25 | |
42 | |
4 |
