Yes, inside the consequence you can use the single parameter modify
because the engine knows how to find the fact handle.
In reality, the modify() block:
modify( $fact ) {
...
}
Is nothing more than a parsing feature that gets rewritten as:
drools.modifyRetract($fact);
...
drools.mod
Edson,
Thanks for the reply. I took a look at your post regarding how to
retract then modify the fact, but I have a different situation. I
need to modify the fact via a function call. This is because inside
the function I have access to Spring-managed services that I use to
retrieve domain obje
It seems the docs need to be updated. Would you plz open a JIRA to fix
the place you are seeing this info?
For more current info, take a look at this blog post, specially the end
on "how to disable shadow facts":
http://blog.athico.com/2008/02/shadow-facts-what-you-always-wanted-to.html
I am currently using Drools to validate an extensive object graph.
When I validate a transient object graph (i.e., not persisted via
Hibernate) inside of a JUnit test method, validation occurs
successfully. However, when I retrieve the same object graph from
Hibernate and subsequently validate it,
