Just out of curiosity, if you change your "modify" block and use an "updeat" instead, does it work?
That's not what is in the doc:
Documentation wrote
>
> All operators have normal Java semantics except for == and !=.
> The == operator has null-safe equals() semantics:
> // Similar to: java.util.Objects.equals(person.getFirstName(), "John")
> // so (because "John" is not null) similar to:
> // "John".equals(person.getFirstName())
> Person( firstName == "John" )
>
And still, actually the MyObject class is actually wrapper to the
ActualObject class. The getters and setters are basically simple wrapped.
--
View this message in context: http://drools.46999.n3.nabble.com/ConsequenceException-when-using-modify-tp3750604p3750755.html
Sent from the Drools: User forum mailing list archive at Nabble.com.
_______________________________________________
rules-users mailing list
rules-users@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/rules-users