This improvement would have two benefits:
- help to work around ROO-581, by removing the need to register null-friendly PropertyEditors for multiple entity classes in multiple controllers
- conform more closely to Postel's Law: "be conservative in what you do, be liberal in what you accept from others"
At the moment, Roo generates this finder in Pizza_Roo_Entity.aj:
This code would be more usable if it gracefully accepted a null id, as follows: