Hallo Edson
Im not going to pretend i understand all the details about the
shadow facts, but
i think you mean there needs to be a layer between the asserted
beans and the
engine to control when changes to the beans have an effect upon
the engine, e.g. with
then
$foo.setBar(123)
...
Is this not similar in principle to my
problem, where I do have simple getters but those getters return an object
reference that Id like to run a rule against?
For example:
public class Bar {
private Foo foo;
public Foo
getFoo() { return foo; }
}
public class Foo {
private
You cant yet do anything like:Bar(foo.tuo == ...)but you can doBar($foo: foo)eval($foo.getTuo().equals(...))I think its a seperate problem.
On 10/27/06, Mark Emeny [EMAIL PROTECTED] wrote:
Is this not similar in principle to my
problem, where I do have simple getters but those
You cant yet do anything like:Bar(foo.tuo == ...)
but you can
doBar($foo: foo)
eval($foo.getTuo().equals(...))
I think its a seperate problem.
Hmmm I think our problems might be at least related.
If i understand it right, the reasons you cant do something like
Bar(foo.tuo == ...)
is
yes you are correct. a. is true, but solvable (we will solve it - but it will still be about navigating an object graph).b. yes that is true, and this is the more sensitive one. Basically if you use deep nested structures, there may be performance impacts no matter what.
So the moral, is flatten
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
hello,
sure. But the problem is, I need a rule which fires exactly once for any
existance of a
$r : Relation()
...where additional constraints are true, namely:
forall $a : Attribute( relation == $r ) (
forall InclusionDependency ( r1 == $r, a1
Mark,
For now you have to do as Michael said, but trunk already has (for
the next version) the from operator:
when
Foo( tuo == ... ) from Bar.getFoo()
then.
...
end
[]s
Edson
Michael Neale wrote:
You cant yet do anything like:
Bar(foo.tuo == ...)
but you can do
Bar($foo:
Hey Trevor,
You got the idea about shadow facts. Just a minor comment, instead
of intercepting set methods and business methods, what we do is we
cache get methods (it means, any parameterless method with return type
!= void).
From your explanation, my understanding is that what
Title: Global and Working Memory View
I'm having problems about getting my global data and working memory view working when I'm running a debug session in eclipse. I've downloaded the plugin and copied the jar file into the plugins directory in eclipse. I'm able to create a new rules project
You have to select a WorkingMemory instance.
Chan, Philip wrote:
Global and Working Memory View
I'm having problems about getting my
global data and working memory view working when I'm running a debug
session in eclipse. I've downloaded the plugin and copied the jar file
into the
10 matches
Mail list logo
