Hi Mario,
is there any progress? Could you find anything?
Best,
Josep
--
View this message in context:
http://drools.46999.n3.nabble.com/Rules-don-t-execute-using-MVEL-syntax-in-LHS-Possible-Bug-tp4029494p4029581.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
Hi Josep,
as I anticipated the propName vs. getPropName() issue was only a red herring
and totally unrelated with the actual bug. Investigating in more detail your
test case I found that the problem is that in some circumstances, when using
fireUntilHalt, a single working memory action
Hi,
I updated my test code to use your way of creating the Knowledge Base (using
KieBase) and I have the exact same results. Does anyone have an idea why
this is still failing?
Furthermore, I think the way I was initializing my rules is also supported
by Drools 6, because it's almost copied line
Repeated executions show varying results: sometimes it's OK, sometimes it isn't.
I don't think it's a race condition in your code (although proper
syncing on the map would be the clean way to go).
I think that salience doesn't work properly )(6.0.0, OP used 6.0.1.),
if a fact is matched
Hi,
I also thing there is something buggy with salience and the planner.
However, what puzzles me is that this behavior is changed when using the
getter instead of the direct access to the property.
Do you know if there is already a reported bug like this? If there is none,
I will create one.
Hi Josep,
probably there are 2 different issues here, but I am not sure because I
haven't run your test case yet. I'll do it asap.
The first issue could be something similar to what has been already reported
here https://issues.jboss.org/browse/DROOLS-311
As for the different behaviour you
Anytime!
I'll keep an eye on this :)
Thanks for time!
Josep
--
View this message in context:
http://drools.46999.n3.nabble.com/Rules-don-t-execute-using-MVEL-syntax-in-LHS-Possible-Bug-tp4029494p4029524.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
On 12/05/2014, jlprat jlp...@gmail.com wrote:
Hi,
I also thing there is something buggy with salience and the planner.
However, what puzzles me is that this behavior is changed when using the
getter instead of the direct access to the property.
Do you know if there is already a reported bug
Ah yeah, sorry I forgot about this Map.
If you remove it and you just print in the standard output, you have the
same behavior. I just used a map to have something to assert against, this
test code it's not the best code I ever wrote
Josep
--
View this message in context:
Hi all,
I'm developing an application with Drools 6.0.1.Final and I'm encountering a
really strange problem I can't understand, and which I think it's due to a
bug in MVEL.
I'm running some rules using fireUntilHalt and if I use the MVEL syntax
withing the RHS to access some bean properties,
MVEL has nothing to do with the possibility of using abcXyz in a
constraint instead of the more cumbersome getAbcXyz(). Actually,
abcXyz is the native way of accessing a fact's attribute from within
DRL patterns.
So, if getAbcXyz() works, but abcXyz does not, I suspect that
something else is
Hi,
I added the AnEvent class in the gist. You can check it out now:
https://gist.github.com/jlprat/f20e6dbe976cff163d2c
Best,
Josep
--
View this message in context:
http://drools.46999.n3.nabble.com/Rules-don-t-execute-using-MVEL-syntax-in-LHS-Possible-Bug-tp4029494p4029496.html
Sent from
You are using a class called KnowledgeBuilder. With Drools 6,
it is KieBuilder. Here is some simple code, good for testing (as I used it),
although more sophisticated build procedures are recommended
using maven and what not. - Both DRL versions (getAbxDef and abcDef) appear to
work with 6.0.0
13 matches
Mail list logo
