-08-08 15:26 GMT+02:00 Davide Sottara dso...@gmail.com
mailto:dso...@gmail.com:
If I remember correctly this is a known issue. Unfortunately
drools 5.6 is final and can't be patched. Downloading the
source drl rather than the compiled pkg could be a workaround
If I remember correctly this is a known issue. Unfortunately drools 5.6 is
final and can't be patched. Downloading the source drl rather than the compiled
pkg could be a workaround.
Please let me know if it works
Sent via the ASUS PadFone X, an ATT 4G LTE smartphone
Original Message
It has almost certainly been fixed in 6.1
Davide
On 07/31/2014 03:40 AM, David Zeigler wrote:
Hi,
I'm using drools 6.0.1.Final. I received a NPE in
the org.drools.core.common.LeftTupleSetsImpl.removeUpdate() method on
line 172, which corresponds to this line for 6.0.1.Final:
a
clever technique they've used in the past?
Thanks
Borris
On 22/07/2014 17:16, Davide Sottara wrote:
The case may not be supported, but even then, it should be reported as
a compilation error, not as a NPE
I'll investigate and report back later
Thanks
Davide
On 07/22/2014 05:48 PM
Fixed, in PR status. It was indeed another bug.
https://github.com/sotty/drools/commit/7941a0c8d7e66c6c7719c14ca58d798337d067d8
Thanks for reporting, we really appreciate the feedback
Davide
On 07/23/2014 10:58 PM, Borris wrote:
On 22/07/2014 22:44, Mark Proctor wrote:
Stack trace shows the
Declared types support annotations. You'll have to import it
package my.drl;
import my.SomeAnnotation;
declare Foo
@SomeAnnotation
bar : String
end
When the declare is processed, the class builder will try to resolve the
annotation
and, if found, will wire it to the class being generated.
You can add rules programmatically to an existing KieBase, but you have to:
1) add/replace the resource in the KieFileSystem
2) Cast the KieBuilder to InternalKieBuilder and use the
incrementalBuild() method
3) Enjoy and report problems as this is a newer feature
See the test suite here
The case may not be supported, but even then, it should be reported as
a compilation error, not as a NPE
I'll investigate and report back later
Thanks
Davide
On 07/22/2014 05:48 PM, Borris wrote:
I was experimenting with ways of avoiding having to put literal strings
into my rules (it is very
Ack'd and queued.
On 07/22/2014 11:46 PM, Kent Anderson wrote:
It appears there is another condition where Drools holds onto memory
indefinitely. (See https://issues.jboss.org/browse/DROOLS-516)
Use case: We have a set of rules designed to detect a heartbeat, then
report when/if the
Thanks for the feedback! The defeasible subsystem is still very
experimental,
and it's good to know that people are using it.
This said, as for your question. It is possible, but takes a little
effort since we
don't have a public API for that. You can do:
// get the handle for the object
for the response!
A quick question on your example code before I try it:
On 21/07/2014 21:24, Davide Sottara wrote:
Notice that negatively asserted facts end up in a negative entry
point, so you have to look them
up explicitly:
InternalFactHandle negHandle = (InternalFactHandle
Not checking for nulls is a debatable behavior :)
In 5.6 you should be able to use the null safe accessor
Business activity.!status == ...
Which will be rewritten to do the check for you
On Jul 16, 2014 4:33 AM, braveheart85 andrea.pacifico...@gmail.com
wrote:
Yesterday I tried version 5.6. I
Oops, it's !., not .!
On Jul 16, 2014 5:39 AM, braveheart85 andrea.pacifico...@gmail.com
wrote:
I have tried your hint and i got:
query dis
$result : PersonData( businessActivity.!status == CLOSED)
end
[48,38]: [ERR 101] Line 48:38 no viable alternative at input '.' in query
[0,0]: Parser
What are you trying to do exactly when you clear the knowledge base?
If you need to replace all the rules, I'd just create a new KB altogether..
facts would be reasserted into the new rules anyway.
If you need to update some of the rules, Drools 5.x had the KnowledgeAgent
for this purpose. To be
Conceptually you are right, but in practice, when you add a rule/query
to the KBase all the available facts are propagated through the newly
built piece of RETE. Since you clear all the rules first (which has some
cost)
and then you build a new set of rules, the effect is very similar - only,
the
Can you try 5.6 or a later version?
That part of logic was improved in 5.6, and rewritten in 6.x
Davide
On 07/14/2014 04:54 PM, braveheart85 wrote:
I forgot to say what version I'm using. The version of Drools is 5.5.
--
View this message in context:
know what else we can do to facilitate fixing this issue.
On Jul 14, 2014, at 2:09 PM, Davide Sottara dso...@gmail.com wrote:
I'd need to check, but if you can put together the basics of the test
case - the combination of rules and facts that causes the leak,
we'll add the checks to ensure
Thanks for reporting, we'll investigate both this and 498
Davide
On 07/11/2014 08:38 PM, Kent Anderson wrote:
We have found a workaround that eliminates the leftover event (gone
from Working Memory, but not from the JVM memory):
The rule forget it ever happened (seen below) causes the
.
I'll check the enabled attribute's behavior in 6.x
Thanks
Davide
On 07/07/2014 06:11 PM, Borris wrote:
On Monday 07/07/2014 23:26, Davide Sottara wrote:
I'll try to reproduce the exception with the rule and the data model.
Meanwhile, could you share a self-contained unit test that reproduces
, Borris wrote:
On Wednesday 09/07/2014 14:41, Davide Sottara wrote:
Sorry for not being able to get back to you again earlier.
Yes, the rule / query you are showing makes sense - I would have asked
you for something similar :) It is definitely a bug in the resolution of
the class that defines
What is the relationship (extends/implements) between the classes/interfaces
in your model - ContextFoodItem, FoodItem, ContextDiner, etc.. ?
Could you also please specify the version of Drools you are using?
Thanks!
Davide
On 07/07/2014 03:04 PM, Borris wrote:
I am getting an unexpected cast
I'll try to reproduce the exception with the rule and the data model.
Meanwhile, could you share a self-contained unit test that reproduces
the problem?
That would speed up the fix process
Thanks!
Davide
On 07/07/2014 04:24 PM, Borris wrote:
On Monday 07/07/2014 23:09, Borris wrote:
Hi,
5.5 was not thread-safe and some of these concurrency issues have been
fixed in later versions.
Could you try 5.6 or 6.x?
On 07/02/2014 08:19 AM, maruthi_s wrote:
Hi ,
We use Drools 5.5 and drool implementation is done through Spring
JSR94Support API
The Rule engine is called in concurrent
can you please open a jira ticket and possibly add a reproducer?
It seems a serious regression, but it would have to be reproduced
and fixed in the next few days for this to make it to the final release
Thanks!
Davide
On 06/18/2014 03:26 PM, rogerL wrote:
After upgrade to 6.1.0.CR1 rule
The whole point of @propertyReactive is to avoid no-loop where possible.
What Wolfgang was trying to say is that there is no need to use the eval:
just write
DvFacts0( condIsNUMERIC == null )
and the @propertyReactivity will work
Davide
On 06/11/2014 10:40 AM, brachi wrote:
so, will no-loop
Could you please show the conditions for which you need the eval?
And which version are you using? As far as I know, eval is rewritten and
removed internally in latest versions, so there shouldn't be a difference.
On 06/11/2014 12:34 PM, brachi wrote:
I need the eval.
I have some rules that
I think I know what is happening here.
I assume your supportFT class is @propertyReactive.
(btw, you should follow bean conventions and capitalize class names)
Looking at Rule 1, you don't set the value directly, but you do it through
a modify. Your rule 2, which checks for the value, uses the
java.util.Collections (and descendants) are not @typesafe by default,
I'll check the reason for that.
More generally, if a fact is declared as not @typesafe, the runtime
failure should be more graceful.
Davide
On 06/10/2014 01:26 PM, Wolfgang Laun wrote:
Consider:
class Foo { /*...*/ }
In fact what we have now is *NOT* graceful
I'll open a JIRA and try to provide a fix
On 06/10/2014 01:52 PM, Wolfgang Laun wrote:
On 10/06/2014, Davide Sottara dso...@gmail.com wrote:
java.util.Collections (and descendants) are not @typesafe by default,
I'll check the reason for that.
OK
idea would be using some Java proxy voodoo-magic to wrap
objects before they are inserted to the session, but my gut feeling is
that it would be a way to debug hell...
What do you think?
Cheers,
Peter
2014-05-27 19:42 GMT+02:00 Davide Sottara dso...@gmail.com
mailto:dso...@gmail.com
Both should fire when there is no message.
This said, the two are not equivalent.
The negation of
Message( sent == true, status != INITIALIZED )
is:
Message( sent == false *||* status == INITIALIZED )
That is, by deMorgan's laws, you need to negate
the operators AND flip the and/or connectives.
We are working on the trait framework for cases like this. Essentially,
it allows to use
interfaces when writing rules AND to inject the interfaces dynamically
at runtime,
at the instance level. It relies on transparent proxies which wrap the
data classes
and implement the required interfaces. A
You mean that it used to work with your combination (jboss 4.2 + drools
5.4.0)
and then it suddenly started throwing the exception?
It seems strange.. do you have other applications deployed on the same
instance
of jboss? Maybe it's picking up a different version of the jars from
somewhere else
Could you please show the code where you persist, reload and invoke
fireUntilHalt() on the session?
Ideally, could you open a jira ticket and post the code there? We'll
take a look then.
Thanks
Davide
On 05/22/2014 01:43 PM, rogerL wrote:
Due to an issue with reloading persisted sessions that
but not with jboss.
But using only that dependency fixed the issue. Do you know why?
El may 26, 2014 11:02 AM, Davide Sottara dso...@gmail.com
mailto:dso...@gmail.com escribió:
You mean that it used to work with your combination (jboss 4.2 +
drools
5.4.0)
and then it suddenly started
In the end it was actually named @PropertyReactive
On 05/21/2014 12:38 AM, RavishankarHassain wrote:
I was looking fro some examples and document which explains on how to use the
@Modifies annotations inside Facts(Java class) and it happened for me to see
this doc
Bugs about @PR were reported and fixed in 5.6 and 6.x
The fixes cover the bug described in the original thread.
More issues related with @PR were fixed here:
https://issues.jboss.org/browse/DROOLS-91?jql=project%20%3D%20DROOLS%20AND%20text%20~%20%22property%20reactive%22
If you have encountered
This is unlikely a problem of the guided editor. Tuples are created when
you run the rules in a session.
We'd need to know which rules you're running and how you are
inserting/retracting facts.
Best
Davide
On 05/01/2014 01:57 PM, Jens Alejos at OAK CORP x4287 wrote:
Hello,
Our Guvnor
On 05/01/2014 09:46 PM, Wolfgang Laun wrote:
A window:length is filled depending on the constraints but independent
of how old the participating facts are.
Currently only ALPHA constraints determine which facts are
filtered by a length window. There is a JIRA to include beta constraints,
but it
Looks like a bug.. can you post the DRL that generates this error?
On 04/15/2014 09:12 AM, lvtenorio wrote:
Hello,
I am writing a rules file and unit tests to test each one of them. I am
getting this error during the execution
java.lang.VerifyError: Bad type on operand stack
Exception
Ok, perfect. That internal interface was indeed changed.
Please note that there is a potential problem with the implementation of
the
custom evaluators in 5.6. It has been fixed in 6.x, but it should
probably be backported. Let me know if you have problems.
Davide
On 04/14/2014 08:29 AM, Cwen
Are you downloading a compiled PKG resource? You'd have to rebuild
the PKG with 5.6, or use the source DRL..
On 04/14/2014 11:08 AM, Cwen wrote:
Davide,
I tried change our methods signature and run the application. Getting
following stack trace when calling
MVEL glitch, try size() 0
On 04/14/2014 11:59 AM, Cwen wrote:
Thank you Davide. That helped. I re-compiled the pkg and it got loaded
successfully. However the run execution is throwing the following errors. I
am looking into it. Not sure if that's something you have any insight.
[Error:
Strange.. the APIs should have not changed between 5.5 and 5.6...
what kind of compilation errors are you getting exactly?
1) The KA was partially rewritten because of a sub-project (drools-mas),
so it was a combination of fixes and natural evolution
You can try the tickets here, however:
Can you try 5.6.0.Final?
Many issues regarding the KnowledgeAgent were fixed in that version
Thanks
Davide
On 04/11/2014 08:45 PM, Cwen wrote:
View this message in context: Re: KnowledgeAgentImpl
registeredResourceMap
Can you upgrade to 5.6?
Otherwise, you'll have to synchronize the methods int ClassLoader, the
null check is not enough
On 04/04/2014 09:16 PM, Karan Malhotra wrote:
Hi All,
We have recently upgraded our application from 5.1.0 to 5.4.0.Final.
Everything worked well until this was
You should look at the 5.6 series, not the 6.0. Too many things have changed
in the latter
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Linkage-Error-In-execute-method-tp4029123p4029130.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
I think I'm starting to see the problem now. Where does this component live
exactly, and how is that (and the KB) shared between your different webapps?
--
View this message in context:
http://drools.46999.n3.nabble.com/rules-users-Memory-leak-due-CompositeClassLoader-tp4029053p4029131.html
You may have to dispose the sessions explicitly - or even the knowledgebase,
using the internal method that was added as a temporary brute force patch
to leaks in 5.6.
The composite classloader was replaced in 6.x, so the newer versions should
not have this kind of problems.
Best
Davide
--
View
Can you try 6.1.0-SNAPSHOT?
I tried your code quickly and it seems to work
Davide
On 03/20/2014 03:25 PM, GrantWang wrote:
Would someone please help with this? Did I do something wrong or is this a
bug? I am using 6.0.1. Thanks!
--
View this message in context:
Can you try version 5.6?
On 03/19/2014 05:27 PM, alineasol wrote:
Hello,
We have a KnowledgeAgent with this configuration:
* drools.resource.scanner.interval = 900
* drools.agent.monitorChangeSetEvents = true
* drools.agent.scanResources = true
*
this it
goes.. so when i create more than 4 files all at the same instant it
falls under the same session and the sliding window works..
could this be the problem?
On Mon, Mar 17, 2014 at 5:28 PM, Davide Sottara dso...@gmail.com
mailto:dso...@gmail.com wrote:
It is possible to declare sliding
It is possible to declare sliding windows
A possible problem (I didn't check the logic) is that
you are not inserting the new Events you create.
On 03/17/2014 12:13 PM, Sandhya Sree wrote:
i found this type of declaration in a site and thought this is allowed..
also it doesnt throw any
in a current technology stack which i am using currently
using strom - drools- saving back to database.
Regards,
Raj
On 14 March 2014 19:59, Davide Sottara dso...@gmail.com
mailto:dso...@gmail.com wrote:
+1 Wolfgang :)
Raj,
we'd need
loosing the session since i am running is
multi-threaded environment
I see the following URL
https://github.com/droolsjbpm/drools/pull/256/files
Are these changed to main branch for version 6.0.1
Regards,
Raj
On 13 March 2014 23:46, Davide Sottara dso...@gmail.com
mailto:dso...@gmail.com
are processing a set of 500 records, 250 are
getting processed and 250 are getting failed
Please suggest
On 14 March 2014 15:53, Davide Sottara dso...@gmail.com wrote:
Major bugs are usually backported.. are you sure that this fix addresses
your problem?
In general, if you don't provide
Are you using stateful or stateless sessions?
Davide
On 03/13/2014 05:01 PM, Raja Sekhar wrote:
Hi
Can someone help me with this.
Regards
Raj
On 13 March 2014 14:05, Raja Sekhar raja.amir...@gmail.com
mailto:raja.amir...@gmail.com wrote:
Hi
Iam processing dataset stream
The ResourceChangeScanner will consider a resource modified if last
modification last read.
If your resource is a URL resource pointing to a file, the
implementation (version 5.6, at least)
will delegate to File.lastModified().
Make sure that whenever you (re)deploy your PKGs, the lastModified()
The accumulates should not be in the then part of a rule (see my
previous email).
That rule gave you two lists, in the variables $plus and $mins, that you
can use in the consequence.
If you need to process each file separately, you may want to do
something like this:
rule new file
when
if 3 new files are
added, 3 event objects must be created, and all three event objects
must be added to ListEvent listOfEvents.
Thanks.
On Mon, Mar 10, 2014 at 11:48 PM, Davide Sottara dso...@gmail.com
mailto:dso...@gmail.com wrote:
The accumulates should not be in the then part
If I remember correclty, extension only works within the same package
On 03/06/2014 05:08 PM, SrjTx wrote:
BaseRule DRL is
package com.xyz.cep;
import com.xyz.model.Flow;
declare Flow
@role(event)
end
rule BaseRule
dialect java
when
then
end
Similar bugs have been fixed over different versions, but
it's very difficult to tell without some context.
One would need at least the rule that causes the exception,
but a minimal reproducer (rules + facts) would be ideal.
On 03/05/2014 11:12 AM, Wolfgang Laun wrote:
Could be a bug that has
Thanks, we'll look into this as soon as possible!!
Davide
On 03/04/2014 06:46 PM, ters wrote:
Davide Sottara wrote
However, the *deadlock* situation might have exposed a bug.
Could you please submit a self-contained reproducer?
Davide, I've posted on forum new topic with complete example
Evaluators are typically registered in the packagebuilder.conf file,
or passed to the packagebuilder. Did you do something equivalent in guvnor?
On 03/04/2014 05:46 PM, mattmadhavan wrote:
Hello,
I have written a custom operator called inlist and it works great in 5.4.0
(not in 5.6.0).
When
Raja,
it is not clear what you are trying to achieve.
The rule might be well written or not, we don't know your requirements.
If id is what it should be - an identifier - your accumulate constraint
would match a single object for each Product (the original product itself),
which looks suspicious.
from product group by hild
so i will get
if the data is
hlid t1
110
110
2 10
2 10
the result would be
hiid t1
1 20
2 20
Hope you understand what i am trying to do here
Regards,
Raja
Regards,
Raja
On 3 March 2014 17:05, Davide Sottara dso...@gmail.com
There are a few errors in the rules
1)
not FileData( fileOld == fileNew )
will fire either 1) when there is a FileData with different lists OR 2)
when there is no FileData at all in the workingMemory
2)
the rule should not compile, unless fileOld and fileNew are STATIC
fields of the class
Could you please share the unit test?
Thanks
Davide
On 02/27/2014 11:42 AM, Brecht De Rooms wrote:
Dear Drools users,
I just merged all my code to Drools 6.0.1 and I am happy to see that it is
more stable. Several issues I had with 5.6.x do not present themselves in
6.0.1. I am still
We could reproduce the issue, it's now in a unit test:
https://github.com/droolsjbpm/drools/pull/317/files
Thanks for reporting this!!
Davide
On 02/28/2014 12:44 AM, mikerod wrote:
I made a basic jar that only depends on Drools.
All the rules do is output to standard out to demonstrate.
This
I think I see the problem - though I haven't been able to test it with
guvnor.
Property Reactivity is resolved at compile time, when the package is built.
When you load the DRL, you set PropertyReactive.ALWAYS in the (local)
KnowledgeBuilder, so it will consider all classes as PR.
However,
ProperReactive to the classes(in the sample project).
Davide Sottara wrote
I think I see the problem - though I haven't been able to test it with
guvnor.
Property Reactivity is resolved at compile time, when the package is
built.
When you load the DRL, you set PropertyReactive.ALWAYS in the (local
5.6.x is the master of the 5.x series..
5_6 dynamic is a temporary branch, created for development or test purposes,
which has never been deleted
On 02/26/2014 09:59 PM, dunnlow wrote:
What is the difference between the 5.6.x and 5.6_dynamic branches in github?
Thanks,
-J
--
View this
Yes, instead of the URL
http:// ... /packages/ [my pack ] / binary
use
http:// ... /packages/ [my pack ] / source
On 02/26/2014 10:24 PM, gboro54 wrote:
Is there a way to download the drl of a snapshot? I know you can see the
rules in the Guvnor(uneditable of course) but is there a way to
You likely have configured a DebugAgendaEventListener, which logs agenda
events (rules activated, fired, etc..)
on the standard error rather than the standard output. If you want a
different behavior, remove the listener
and implement one of your own.
These are not errors anyway.
Davide
On
Davide Sottara dso...@gmail.com
mailto:dso...@gmail.com:
You likely have configured a DebugAgendaEventListener, which
logs agenda events (rules activated, fired, etc..)
on the standard error rather than the standard output. If you
want a different behavior
Persisting sessions manually, especially out of synchronization and
transactions, is not recommended.
As previously suggested by Mario, could you try the JPA Persistent Sessions?
However, the *deadlock* situation might have exposed a bug.
Could you please submit a self-contained reproducer?
Interesting.. this may be a bug in the serialization process, and it may
affect 6.x too
Could you please check it with a package that contains a single rule
using a single
@propertyReactive class?
On 02/25/2014 09:25 PM, gboro54 wrote:
Also note we are using property reactive listener always.
Thanks!
I'll get back to you tomorrow with the results
On 02/25/2014 11:53 PM, gboro54 wrote:
test-drools.zip
http://drools.46999.n3.nabble.com/file/n4028329/test-drools.zip
Here is a sample project which shows the issue. You can build the project as
the fact model and upload the drl into
Please open a JIRA ticket, this is the way bugs are reported to the
development team.
https://issues.jboss.org/browse/DROOLS
Davide
On 02/20/2014 03:38 PM, droolster wrote:
@laune, any update? Should I post to Stackoverflow as you are active there.
Is this forum dead?
--
View this
Could you provide a full reproducer: rules, java snippet and stack trace
of your exceptions?
As a side note, is the path correct? dymanic looks like a typo..
Thanks
Davide
On 02/17/2014 09:34 AM, Raja Sekhar wrote:
Hi
i am trying to use drools template
String drl =
Unfortunately I am not completely surprised... ironically, that function
signature was changed at some point to simplify the code and make it more
robust internally.
The change, however, broke the backwards compatibility with existing custom
implementations (something the users can fix) and the
Matt, I had answered another thread directly on the forum, I'm not sure
that it made it to the user list.
This was my answer:
Unfortunately I am not completely surprised... ironically, that
function signature was changed at some point to simplify the code and
make
Could you please show the stack trace of the exception and the rule that
causes it?
Thanks
Davide
On 02/14/2014 02:38 AM, mattmadhavan wrote:
Hello,
I am having a hard time with a custom operator. It works great in 5.2 but
not in 5.6. Do you mind sharing your email ample for 5.6 please? I
I can see a few independent issues here.
Drools 5.x was not designed to be thread-safe in general: there are some
known
critical races that may arise when multiple threads are inserting
facts in parallel. Many have been patched in 5.6, but the real
solution to the problem will be introduced in the
It is a bug, I'd say related to constraint jitting..
It seems to work with 5.6.0.Final, could you please try that version?
Thanks
Davide
On 02/10/2014 06:06 PM, antoine wrote:
Hello,
I've faced some weird result using Drools 5.5.0.Final, and I would like to
know if I am doing something wrong
as reported by abr. I work with abr on the
project :) As he could not reproduce the bug, I just removed lines of
code as much as possible to keep only the essentials. Here is a unit
test:
Drools-after.zip
http://drools.46999.n3.nabble.com/file/n4027676/Drools-after.zip
Davide Sottara
Thanks,
today we have actually identified the real cause of the error
and we are already working to get it fixed.
I wonder if a cast would also work :
MyType( (Boolean) global_invoke( this ) )
Davide
On 01/30/2014 10:03 PM, mikerod wrote:
Thank you for your reply. That was helpful. I did
Could you post the full test case (rules + java)?
Thanks
Davide
On 01/28/2014 05:10 PM, jhusby wrote:
I'm trying to stress-test Drools to see what its limits are, and I stumbled
across a NPE when I have a large amount of facts in a stateful
knowledgebase:
java.lang.NullPointerException
Declared types have public accessors as usual.
This seems a minor bug in the expression analysis.
Can you try
getRaw().complicated()
and / or
raw.complicated
and report what happens?
Thanks
Davide
On 01/23/2014 06:40 AM, pmander wrote:
If I declare a type in a drl and reference the
In that case I'm almost sure that the whole constraint has to be treated
as a java expression.
So yes, you will probably need getRaw().complicated( ... )
On 01/23/2014 08:06 AM, pmander wrote:
will do, although complicated() has parameters and so I think I'll only able
to try
Yes, if you use the java dialect, the whole RHS is parsed as a java block
with some minor syntactic sugar (e.g. insert).
On 01/23/2014 08:46 AM, pmander wrote:
Davide Sottara wrote
Declared types have public accessors as usual.
This seems a minor bug in the expression analysis.
Can you try
There may be some misunderstanding here..
you can indeed rebuild the jar, but there is also a programmatic
way to add (DRL) resources to an in-memory FS and update
the KBs/KSs on the fly. See the examples in IncrementalCompilationTests
Davide
On 01/23/2014 10:11 AM, Mark Proctor wrote:
On 23 Jan
I'd say it's a bug... maybe indexing is involved?
Replacing ruleA's LHS with
$p: Parent( $a2 : attribute2 != null)
?getChildWithName($a2 , n1, $child;)
makes it work as expected. I will investigate further.
Davide
On 01/22/2014 02:22 PM, Esteban Aliverti wrote:
Hi guys,
I was writing
Indeed, the use case can be simplified further:
package org.drools.test.bc;
declare Parent
attribute2 : String
end
declare Child
parentId : String
end
query getChildWithName( String $parentId, Child $child )
$child:= Child( parentId == $parentId )
end
rule Insert Children
when
Actually (and arguably) I think that the behavior is consistent.
In the first case, you insert a MyClass instance: base is eligible
for activation, and so is rule 1. When rule 1 fires, it inserts a String
which continues the previous propagation through rule 2. At this
point, value is still !=
under drools 5.5.0.Final.
Caused by: java.lang.NullPointerException at
org.drools.base.evaluators.AfterEvaluatorDefinition$AfterEvaluator.evaluate(AfterEvaluatorDefinition.java:347)
at org.drools.base.EvaluatorWrapper.evaluate(EvaluatorWrapper.java:99)
Davide Sottara wrote
I tried
of vacuous implications :
if donkeys could fly then (anything you want here)
these are trivially true, too
Davide
On 01/08/2014 09:28 AM, Wolfgang Laun wrote:
On 08/01/2014, Davide Sottara dso...@gmail.com wrote:
Indeed it is true by convention, see also
http://en.wikipedia.org/wiki
that
it would be appropriate to change it.
Davide
On 01/08/2014 12:32 PM, Sonata wrote:
laune wrote
On 08/01/2014, Davide Sottara lt;
dsotty@
gt; wrote:
Indeed it is true by convention, see also
http://en.wikipedia.org/wiki/Universal_quantification
The only other alternative is to deprecate
The all and some combination is actually quite popular and might
be implemented at some point. By no means it is the only possibility
to enhance the expressivity of the language:
http://plato.stanford.edu/entries/generalized-quantifiers/
On 01/08/2014 01:50 PM, Sonata wrote:
Davide Sottara
First order logic does permit empty domains, and the universal
quantifier evaluates to true in that case.
Davide
On 01/07/2014 11:11 AM, Wolfgang Laun wrote:
It is true that first-order logic usually assumes that the domain of a formula
be a nonempty set. As so often, things aren't quite so
1 - 100 of 424 matches
Mail list logo
