The only danger is with generated code, where you don't have full control over the final number of attributes. I would assume that, in those cases, one should avoid @propertyReactive altogether if there is a danger of exceeding the threshold? A warning would be ignored in an automatic developement process, potentially ending in loops where @pR is not kicking in as expected :( This is just for clarity, I do agree on the fact that huge bean classes should be used with care Davide
-- View this message in context: http://drools.46999.n3.nabble.com/rule-infinitely-loops-appears-to-be-depending-on-naming-on-variable-tp4020158p4020172.html Sent from the Drools: User forum mailing list archive at Nabble.com. _______________________________________________ rules-users mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-users
