[drools-dev] janino 2.0.9 and unparse visitor

Mark Proctor <mproctor <at> codehaus.org>
2004-09-09 09:26:59 GMT

Janino 2.0.9 is now available with a working unparse visitor, this
builds on the work in current CVS, so users can now see what the
"synthetic" java looks like. This is where we take the users
condition/consequence and add imports and make application data and
declarations available as variables automagically.

To give you an idea of what the resulting code looks like when its run
I have included some outputs from examples fibonacci, state and
petstore; the petstore example also shows application data being used.

[drools-dev] escalation and trouble ticket

Mark Proctor <mproctor <at> codehaus.org>
2004-09-10 02:03:15 GMT

New example "escalation" in cvs for java that demonstrates the Duration
semantic, which I just got working again. Any volunteers to convert to
groovy and python, likewise docs for this in the normal step by step
fashion would be great :) Base Semantic Module docs also need updating
to detail the Duration element.
Mark

[drools-dev] CVS Progress Update

Mark Proctor <mproctor <at> codehaus.org>
2004-09-13 11:22:12 GMT

I have put together a progress updating for most of the work in CVS
since the last beta, which will be included in the next upcoming beta.
-Robust Janino implementation in drools-java for application data and
indentifier variables.
-Python fixes
-Bug fix for recency conflict resolution strategy, breadth/depth were
wrong way around
-Fact based recency now implemented, along side the existing activation
based recency.
-DefaultConflictResolution now implements OPS5 LEX strategy (salience,
rency, complexity, loadorder)
-ConditionException and ExtractionException now have methods to get the
Rule the exception occured in, along with the text for the given expression.
-ConsequenceException now reports the Rule the exception occured in
Regards
Mark

[drools-dev] Re: CVS Progress Update

Mark Proctor <mproctor <at> codehaus.org>
2004-09-13 11:25:29 GMT

Sorry forgot to add that <duration .../> now works and a new example has
been added "elevation-java" to demonstrate this; documentation on this
will be added shortly.
Mark
Mark Proctor wrote:
> I have put together a progress updating for most of the work in CVS
> since the last beta, which will be included in the next upcoming beta.
>
> -Robust Janino implementation in drools-java for application data and
> indentifier variables.
> -Python fixes
> -Bug fix for recency conflict resolution strategy, breadth/depth were
> wrong way around
> -Fact based recency now implemented, along side the existing
> activation based recency.
> -DefaultConflictResolution now implements OPS5 LEX strategy (salience,
> rency, complexity, loadorder)
> -ConditionException and ExtractionException now have methods to get
> the Rule the exception occured in, along with the text for the given
> expression.
> -ConsequenceException now reports the Rule the exception occured in
>
> Regards
>
> Mark
>
>

[drools-dev] Re: CVS Progress Update

Mark Proctor <mproctor <at> codehaus.org>
2004-09-14 20:21:55 GMT

Schemas are now available in CVS and validation is done at rule loading
time.
Mark Proctor wrote:
> Sorry forgot to add that <duration .../> now works and a new example
> has been added "elevation-java" to demonstrate this; documentation on
> this will be added shortly.
>
> Mark
> Mark Proctor wrote:
>
>> I have put together a progress updating for most of the work in CVS
>> since the last beta, which will be included in the next upcoming beta.
>>
>> -Robust Janino implementation in drools-java for application data and
>> indentifier variables.
>> -Python fixes
>> -Bug fix for recency conflict resolution strategy, breadth/depth were
>> wrong way around
>> -Fact based recency now implemented, along side the existing
>> activation based recency.
>> -DefaultConflictResolution now implements OPS5 LEX strategy
>> (salience, rency, complexity, loadorder)
>> -ConditionException and ExtractionException now have methods to get
>> the Rule the exception occured in, along with the text for the given
>> expression.
>> -ConsequenceException now reports the Rule the exception occured in
>>
>> Regards
>>
>> Mark
>>
>>
>
>
>

Re: [drools-dev] Rules w/o Conditions

No objections here. I've had to code many rules with
"<java:condition>true</java:condition>" to get around that limitation.
~Andy
On Sep 16, 2004, at 10:02 AM, peter royal wrote:
> Any objections to allowing rules w/o Conditions?
>
> Bob said it poses no problems.. Since a Fact can be multiple
> ObjectType's at the same time, that's an implicit condition..
> -pete

[drools-dev] Rule-sets w/o Rules

Any objections to allowing Rule-Sets without Rules? I know its a
trivial condition, but I don't see any reason to disallow empty
rule-sets.
I've found in my own work with XML files, it is often helpful to create
such "empty" xml files when testing new code.
Also, the drools-examples primefactors-java example has a placeholder
DRL file with all of its rules commented out, which causes a schema
validation warning when a user runs that example.
~Andy