Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add an option to disable the automatic creation of nested path in DataBinder and subclasses [SPR-6430] #11096

Closed
spring-projects-issues opened this issue Nov 24, 2009 · 1 comment
Assignees
Labels
type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

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

@spring-projects-issues
Copy link
Collaborator Author

Graeme Rocher commented

Related Grails bug http://jira.codehaus.org/browse/GRAILS-4589

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants