Mark Proctor | 1 Apr 11:45 2005

[Fwd: [drools-dev] [jira] Commented: (DROOLS-305) Invalid Handles after calling retractObject in WorkingMemory]

This is the final jira (http://jira.codehaus.org/browse/DROOLS-305)  
holding up the Release Candidate. I need sample code to prove the issue. 
If I dont receive anything within the next couple of days I'm going to 
unschedule it and we do a RC without a fix for it.

I have had no feedback (http://jira.codehaus.org/browse/DROOLS-259) 
other than from Glenn on the JBOSS classloader issue. I will marked this 
as closed early next week unless I am told otherwise.

Mark
-------- Original Message --------
From: 	- Tue Mar 29 02:30:02 2005
X-Account-Key: 	account9
X-UIDL: 	1112055831.26687.beaver.codehaus.org
X-Mozilla-Status: 	0001
X-Mozilla-Status2: 	00000000
Return-Path: 	<dev-return-1581-mproctor=codehaus.org <at> drools.codehaus.org>
Delivered-To: 	mproctor <at> codehaus.org
Received: 	(qmail 26648 invoked by uid 7957); 29 Mar 2005 00:23:51 -0000
Mailing-List: 	contact dev-help <at> drools.codehaus.org; run by ezmlm
Precedence: 	bulk
List-Post: 	<mailto:dev <at> drools.codehaus.org>
List-Help: 	<mailto:dev-help <at> drools.codehaus.org>
List-Unsubscribe: 	<mailto:dev-unsubscribe <at> drools.codehaus.org>
List-Subscribe: 	<mailto:dev-subscribe <at> drools.codehaus.org>
Reply-to: 	dev <at> drools.codehaus.org
Delivered-To: 	mailing list dev <at> drools.codehaus.org
Received: 	(qmail 26545 invoked from network); 29 Mar 2005 00:23:45 -0000
Message-ID: 	<24631972.1112055825221.JavaMail.jira <at> beaver.codehaus.org>
Date: 	Mon, 28 Mar 2005 19:23:45 -0500 (EST)
(Continue reading)

Edson Tirelli | 1 Apr 14:36 2005
Picon

[drools-dev] Pending issue for RC - DROOLS-313

    Hi Mark,

    What about http://jira.codehaus.org/browse/DROOLS-313?
    May I ask you to fix it for the RC? Right now, I have a local 
compiled jar with the quick fix I made to be able to successfuly run our 
system. It would help a lot if I can use the official build instead of a 
local modification.
    I attached a sample code to reproduce the problem in the issue. If I 
can help in any way, just let me know.

    Thank you,
            Edson

Mark Proctor wrote:

> This is the final jira (http://jira.codehaus.org/browse/DROOLS-305)  
> holding up the Release Candidate. I need sample code to prove the 
> issue. If I dont receive anything within the next couple of days I'm 
> going to unschedule it and we do a RC without a fix for it.
>
> I have had no feedback (http://jira.codehaus.org/browse/DROOLS-259) 
> other than from Glenn on the JBOSS classloader issue. I will marked 
> this as closed early next week unless I am told otherwise.
>
> Mark
> -------- Original Message --------
> From:     - Tue Mar 29 02:30:02 2005
> X-Account-Key:     account9
> X-UIDL:     1112055831.26687.beaver.codehaus.org
> X-Mozilla-Status:     0001
(Continue reading)

Mark Proctor | 1 Apr 15:06 2005

Re: [drools-dev] Pending issue for RC - DROOLS-313

OK I've scheduled it for the RC. Now you know what the problem is, any 
chance you can submit a patch? Otherwise I'll see if I can get time to 
do it this weekend.

Mark
Edson Tirelli wrote:

>    Hi Mark,
>
>    What about http://jira.codehaus.org/browse/DROOLS-313?
>    May I ask you to fix it for the RC? Right now, I have a local 
> compiled jar with the quick fix I made to be able to successfuly run 
> our system. It would help a lot if I can use the official build 
> instead of a local modification.
>    I attached a sample code to reproduce the problem in the issue. If 
> I can help in any way, just let me know.
>
>    Thank you,
>            Edson
>
> Mark Proctor wrote:
>
>> This is the final jira (http://jira.codehaus.org/browse/DROOLS-305)  
>> holding up the Release Candidate. I need sample code to prove the 
>> issue. If I dont receive anything within the next couple of days I'm 
>> going to unschedule it and we do a RC without a fix for it.
>>
>> I have had no feedback (http://jira.codehaus.org/browse/DROOLS-259) 
>> other than from Glenn on the JBOSS classloader issue. I will marked 
>> this as closed early next week unless I am told otherwise.
(Continue reading)

Mark Proctor | 1 Apr 15:22 2005

[drools-dev] Re: [drools-user] Re: Can I use duration to implement temporal sequences in rules

Try combining duration with some use of a semaphore to control the 
exucution of the rules. I'm a bit too busy to look into this one in any 
detail at the moment. But it could be a good example and I'll try and 
address it after 2.0 if you are still having problems.

Mark
Olu Oni wrote:

>any comments or thoughts on how to implement a solution to my problem,
>or on the solution i suggest. i really would welcome input from more
>experienced users of drool on this
>
>
>On Tue, 29 Mar 2005 01:02:27 +0200, Mark Proctor <mproctor <at> codehaus.org> wrote:
>  
>
>>Duration executes a rule after a period of time if that rule is still true:
>>http://drools.org/Temporal+Rules
>>http://drools.org/Escalation+Example
>>
>>Olu Oni wrote:
>>
>>    
>>
>>>To further illustrate my question, see below a rough implementation of
>>>the possible solution i mentioned in my earlier post.
>>>
>>>I am wondering if there is a simpler, less costly way - perhaps using
>>>duration in some other way unknown to me - to implement this. I am new
>>>to Drools, so forgive any syntax errors, also pls point out any
(Continue reading)

Edson Tirelli | 1 Apr 15:23 2005
Picon

Re: [drools-dev] Pending issue for RC - DROOLS-313


    Mark,

    I attached the patch I'm using to the issue. It works fine, but I 
don't know if it is the best solution.

    Hope it helps,

     Thanks,
        Edson

Mark Proctor wrote:

> OK I've scheduled it for the RC. Now you know what the problem is, any 
> chance you can submit a patch? Otherwise I'll see if I can get time to 
> do it this weekend.
>
> Mark
> Edson Tirelli wrote:
>
>>    Hi Mark,
>>
>>    What about http://jira.codehaus.org/browse/DROOLS-313?
>>    May I ask you to fix it for the RC? Right now, I have a local 
>> compiled jar with the quick fix I made to be able to successfuly run 
>> our system. It would help a lot if I can use the official build 
>> instead of a local modification.
>>    I attached a sample code to reproduce the problem in the issue. If 
>> I can help in any way, just let me know.
>>
(Continue reading)

Greg Barton | 3 Apr 03:09 2005
Picon

[drools-dev] Ordering of conditions in Annotation Semantic Module rules

Hello. I've got a question about rules defined in
using the  Annotation Semantic Module.  The conditions
created enter the rule in an arbitrary order,
basically however Class.getMethods() orders them. 
Would it be OK to change it so one coudl either 1) by
default order them by the class they were defined in,
from superclass to subclass, then 2) be able to
arbitrarily order them by inserting an attribute into
the DroolsCondition annotation?  I've already modified
AnnonatedPojoRuleBuilder.buildConditions() to do the
former, like so:

private static void buildConditions( Rule rule, Class<
? > ruleClass, Object pojo )
            throws DroolsException
    {
        Map<Method,PojoCondition> conditions = new
HashMap<Method,PojoCondition>();

        for (Method method :
ruleClass.getDeclaredMethods( ))
        {
            DroolsCondition conditionAnnotation =
method.getAnnotation( DroolsCondition.class );
            if (conditionAnnotation != null)
            {
                PojoCondition condition =
newPojoCondition( rule, pojo, method );
                conditions.put(method,condition);
            }
(Continue reading)

Peter Lin | 3 Apr 03:23 2005
Picon

Re: [drools-dev] Ordering of conditions in Annotation Semantic Module rules

there are potential issues with this, since there is patent on rule
inheritance by Pega Systems. Many of the things that can be with rule
inheritance can be done with a good rule editor without rule
inheritance. Obviously, the catch is you have to pay for a good rule
editor.

rule inheritance in practice is more restrictive in the long run.
Lately pega systems has been trying to cash in on the BPM hype. What
ever implementation is chosen, it should attempt to stay clear of
having one rule inherit from a parent rule. Do a patent search for
pega systems and you'll see the patent.

peter lin

On Apr 2, 2005 8:09 PM, Greg Barton <greg_barton <at> yahoo.com> wrote:
> Hello. I've got a question about rules defined in
> using the  Annotation Semantic Module.  The conditions
> created enter the rule in an arbitrary order,
> basically however Class.getMethods() orders them.
> Would it be OK to change it so one coudl either 1) by
> default order them by the class they were defined in,
> from superclass to subclass, then 2) be able to
> arbitrarily order them by inserting an attribute into
> the DroolsCondition annotation?  I've already modified
> AnnonatedPojoRuleBuilder.buildConditions() to do the
> former, like so:
> 
> private static void buildConditions( Rule rule, Class<
> ? > ruleClass, Object pojo )
>            throws DroolsException
(Continue reading)

Greg Barton | 3 Apr 03:25 2005
Picon

Re: [drools-dev] Ordering of conditions in Annotation Semantic Module rules


--- Peter Lin <woolfel <at> gmail.com> wrote:

> there are potential issues with this, since there is
> patent on rule inheritance by Pega Systems. 

Ug.  Patents suck.  How about explicit ordering of
conditions through an annotation property?

Thanks,
GreG

Greg Barton | 3 Apr 03:34 2005
Picon

Re: [drools-dev] Ordering of conditions in Annotation Semantic Module rules


--- Peter Lin <woolfel <at> gmail.com> wrote:

> there are potential issues with this, since there is
> patent on rule inheritance by Pega Systems. 

Maybe you could do it and call it "ripple down rules"
instead of inheritance.  Rule inheritance is only a
subset of the ripple down concept, anyway...

http://research.microsoft.com/users/rherb/ripple_down_rules.htm

There's some prior art for ya. :)

GreG

Barry Kaplan | 3 Apr 16:57 2005

Re: [drools-dev] deprecating drools-annotation

Jeff Brown wrote:
> I understand the drools-annotation is being deprecated in favor of 
> drools-spring.  I think the spring module is useful but isn't the 
> annotation module useful on its own as well?  I am curious to know what 
> is driving the deprecation of the annotation module.

drools-spring supports all the behavior of drools-annotation. In fact the drools-spring code was 
derived from drools-annotation.

--

-- 
barry kaplan
groups1 <at> memelet.com


Gmane