Support for form submissions with field names that follow JavaScript object notation [SPR-9244]

[spring-projects-issues]

Keith Donald opened SPR-9244 and commented

JavaScript/Ajax frameworks such as jQuery serialize Javascript Objects as form parameters using indexed object notation (because in JavaScript, every object acts like a map). For example, the following JS object:

var object = {
  connection : {
    provider: 'facebook',
    user_id: 1256789,
    access_token: 'foo'
  }
}

Gets serialized as form parameters:

connection[provider]=facebook&connection[user_id]=1256789&connection[access_token]=foo

It would be helpful if this format could auto-bind to the root form object's 'connection' property of type JavaBean, which would have nested properties 'provider', 'userId', and 'accessToken'. JSR303 validation could then be easily run against that nested bean's properties for example. BeanWrapper can only map the above to a loosely typed Map now--I have to convert to a strongly typed JavaBean manually.

---

Affects: 3.1.1

Issue Links:

• Provide a way to customize the names of JavaBean properties when they're read and written for data binding purposes [SPR-9242] #13880 Provide a way to customize the names of JavaBean properties when they're read and written for data binding purposes

Referenced from: commits spring-attic/spring-framework-issues@4810d5b, spring-attic/spring-framework-issues@4b7474b, spring-attic/spring-framework-issues@4c4b3ef

[spring-projects-issues]

Rossen Stoyanchev commented

Keith, a very minimal project at the issue repository would be very helpful.

[spring-projects-issues]

Rossen Stoyanchev commented

Corrected the example variable above to match the resulting serialized form.

Although BeanWrapperImpl can map the above to a Map, the more general syntax can include more deeply nested objects. I've created an issue project. The README page contains the output of more examples.

[spring-projects-issues]

Rossen Stoyanchev commented

Since POST and PUT tend to send data in the body of the request, the jQuery .serialize() function is useful mainly for GET requests. Even there having serialized data as request parameters is convenient for simple cases but can get quite ugly (see some of these "extreme" examples).