Oh, ok. Then it is shadow proxy related. :)
Shadow proxies can't override final methods, and if they can't override
them, they can not safely prevent hashcode changes at unsafe points... and
that causes all kind of problems with hashmaps that are used internally.
Drools 5 no longer requi
Sorry for the short answer... busy day.
The main problem with agenda filter is that it is defined in application
code and so creates a dependency in the rules from the application code. So,
you break one of the biggest advantages of rules that is to have a separate
lifecycle for rules. There
Edson Tirelli was heard to exclaim, On 06/24/09 15:43:
> Drools 5 is mostly backward compatible with Drools 4. You don't need
> to migrate to the new API, although it is recommended.
Ahh, that's good to know. You might want to mention that somewhere in the
release notes, or on the website. I
Chris,
I found and fixed the problem you mention and will commit it together
with the fix for this issue.
[]s
Edson
2009/6/24 Chris Richmond
> I have been completely unable to declare a function within my .drl file
> using mvel dialect as well….so I’m very interested in this…
>
>
The Expert User Guide, section 2.5.7.3., Agenda Filters, is probably
what you are remembering. Also, see the javadoc on
org.drools.runtime.rule, interface StatefulRuleSession, method void
fireUntilHalt(AgendaFilter agendaFilter) etc.
-W
On 6/25/09, Chris Richmond wrote:
> Hello,
>
>
>
> I though
*Excellent* description of the system operation and overall and answer to my
question. Thank you very much!
Chris
_
From: rules-users-boun...@lists.jboss.org
[mailto:rules-users-boun...@lists.jboss.org] On Behalf Of Edson Tirelli
Sent: Thursday, June 25, 2009 2:28 AM
To: Rules Us
Ok.well when the recognized expert says something is not their preferred
approach, it begs the question .what is your preferred approach for handling
this?
Thanks,
Chris
_
From: rules-users-boun...@lists.jboss.org
[mailto:rules-users-boun...@lists.jboss.org] On Behalf Of Edson Ti
Brody,
Can you try with Drools 5.0.1 (and corresponding MVEL version) that is
the final community release? There were tons of fixes since the candidate
release.
Let us know if it works.
Edson
2009/6/25 Brody bach
>
> Oh yes, sorry I forgot to mention,
>
> Drools 5.0.0.CR1
> Mvel 2
Oh yes, sorry I forgot to mention,
Drools 5.0.0.CR1
Mvel 2.0.8pre1
Thanks
Edson Tirelli-3 wrote:
>
>Hi Brody,
>
>What versions of Drools and MVEL you are using?
>
>[]s
>Edson
>
> 2009/6/25 Brody bach
>
>>
>> Hi,
>>
>> I have a class which implementes several interfaces
>
Hi Brody,
What versions of Drools and MVEL you are using?
[]s
Edson
2009/6/25 Brody bach
>
> Hi,
>
> I have a class which implementes several interfaces
>
> class MyClass implements interA, interB, interC {
> private String nameA;
> private String nameB;
> private St
Hi,
I have a class which implementes several interfaces
class MyClass implements interA, interB, interC {
private String nameA;
private String nameB;
private String ownString;
public String getNameA(){ ---impl of method from interface interA
return nameA;
Txank you
On Thu, 2009-06-25 at 08:19 -0400, Edson Tirelli wrote:
>
>I added a comment to the JIRA, but replicate it here for
> completeness:
>
> =
> Due to some limitations on the way that Drools 4 handles regexps, we
> had to change the default escaping syntax for regexps, from single
Chris,
Although not my preferred approach, you can use agenda filters as a
parameter to fireAllRules().
[]s
Edson
2009/6/24 Chris Richmond
> Hello,
>
>
>
> I thought I had encountered a sample of performing a:
>
>
>
> session.fireAllRules();
>
>
>
> except on explicit rules or at
Chris,
The decision between A and B must be taken on the basis of: do you need
to join objects from the different streams together? If so, you need A. If
not, better go with B.
Regarding threads, the engine works with a single thread, unless you
activate the KnowledgeBase partitioning op
I added a comment to the JIRA, but replicate it here for completeness:
=
Due to some limitations on the way that Drools 4 handles regexps, we had to
change the default escaping syntax for regexps, from single escape to double
escape. In Drools 5, regexps work exactly like in Java. So, inste
I ran into some problems where a fairly simple rule fails in 5.0.1 and
worked in 4.0.7.
I have created an issue on JIRA
https://jira.jboss.org/jira/browse/JBRULES-2136 and was wondering if
someone else has come across that same type of problem.
The rule is:
package org.drools.rules.test
import
16 matches
Mail list logo
