Is there any particular reason to keep doing things that way? I'd like to see conditions become immutable; it would prevent thinkos like I have discovered while investigating OFBIZ-5659.
I noticed that Adrian removed most of javolution from the entity engine,
just over a year ago. One of the uses was the ObjectFactory pattern.
That is good. However, that change still made use of generic do-nothing
constructors, and init() helper methods.
- EntityCondition, javolution ObjectFactory, immutability Adam Heath
