You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There is a bug in Grails related to the addition of Spring 3 handling of nested object graphs we have our own subclass of WebDataBinder that already handled nested object graphs but also had more inbuilt knowledge of the domain so for example if an association was nullable it wouldn't automatically create the nested object.
The problem is Grails data binder is still doing the right thing in this regard, but when it passes of control the super impl it doesn't have this additional knowledge so its creating the nested object graphs which breaks Grails' data binding.
We need to add the ability to call setAutoGrowNestedPaths on the underlying BeanWrapper instance
Graeme Rocher opened SPR-6430 and commented
There is a bug in Grails related to the addition of Spring 3 handling of nested object graphs we have our own subclass of WebDataBinder that already handled nested object graphs but also had more inbuilt knowledge of the domain so for example if an association was nullable it wouldn't automatically create the nested object.
The problem is Grails data binder is still doing the right thing in this regard, but when it passes of control the super impl it doesn't have this additional knowledge so its creating the nested object graphs which breaks Grails' data binding.
We need to add the ability to call setAutoGrowNestedPaths on the underlying BeanWrapper instance
Referenced from: commits bb97ca3
The text was updated successfully, but these errors were encountered: