DROOLS-5025 solved a case like this by excluding getter property from property reactivity mask.
However, there are still some cases which cause unexpected property reactivity.
For example, the rule below causes an infinite loop with executable model because "name" is considered as modified property.
update() without modify block has the same issue.
In standard-drl (DialectUtil.parseModifiedProperties), "getter + otherMethod" chain is considered that the property is modified. So excutable model follows the same.
However, executable model evaluates all method calls in RHS while standard-drl evaluates only direct statements like "setName("AAA");" or "getName().xxx();". executable model also should follow.