[SPR-6871] Spring MVC regression: binding to indexed properties is broken Created: 18/Feb/10  Updated: 15/Jan/19  Resolved: 20/Feb/10

Status: Closed
Project: Spring Framework
Component/s: Web
Affects Version/s: 3.0.1
Fix Version/s: 3.0.2

Type: Bug Priority: Critical
Reporter: Hans Desmet Assignee: Juergen Hoeller
Resolution: Complete Votes: 3
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
is duplicated by SPR-6921 Indexed properties not set correctly ... Resolved
is duplicated by SPR-7040 form:select 3.0.1 regression bug when... Resolved
is related to SPR-6840 form:checkbox tag creates invalid HTM... Closed
is related to SPR-5382 org.springframework.web.servlet.tags.... Closed
Days since last comment: 4 weeks, 6 days ago
Last commented by a User: true
Last updater: Spring Issuemaster


When you submit a form, with databinding on a command object with indexed properties, the indexed properties of the command object are not filled in.
I think this bug is related to the correction that happened in SPR-6840.
The characters [ and ] are not only removed from the id attrbute of the HTML elements, but also (unnessesary) from the name attribute of the HTML elements.

You can see it happening via next example.
When you type 10 and 20 in the input fields, the output to the console is:

{Belgium=null, Switzerland=null}

while the output should have been

{Belgium=10, Switzerland=20}

The class that acts as command object:
package org.example.entities;

import java.util.LinkedHashMap;
import java.util.Map;

public class Continent {
// key = name of country
// Integer= number of inhabitants
private Map<String, Integer> countries = new LinkedHashMap<String, Integer>();

public Continent()

{ countries.put("Belgium", null); countries.put("Switzerland", null); }

public void setCountries(Map<String, Integer> countries)

{ this.countries = countries; }

public Map<String, Integer> getCountries()

{ return countries; }


The Controller class:
package org.example.web;

import org.example.entities.Continent;
import org.springframework.stereotype.Controller;
import org.springframework.ui.Model;
import org.springframework.validation.BindingResult;
import org.springframework.web.bind.annotation.ModelAttribute;
import org.springframework.web.bind.annotation.RequestMapping;
import org.springframework.web.bind.annotation.RequestMethod;

public class ContinentController {
@RequestMapping(value = "/continent.htm", method = RequestMethod.GET)
public String continentForm(Model model)

{ Continent continent = new Continent(); model.addAttribute(continent); return "continent.jsp"; }

@RequestMapping(value = "/continent.htm", method = RequestMethod.POST)
public String continentForm(@ModelAttribute Continent continent,
BindingResult bindingResult)

{ System.out.println(continent.getCountries()); // Here you can see the bug return "continent.jsp"; }


<?xml version="1.0" encoding="UTF-8"?>
<%@page contentType="text/html" pageEncoding="UTF-8" session="false"%>
<%@taglib prefix="c" uri="http://java.sun.com/jsp/jstl/core"%>
<%@taglib prefix="form" uri="http://www.springframework.org/tags/form"%>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN"
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="nl" lang="nl">
<title>Continent example</title>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />
<form:form commandName="continent">
<c:forEach items="${continent.countries}" var="entry">
<form:label path="countries[${entry.key}]">${entry.key}</form:label>
<form:input path="countries[${entry.key}]" />
<form:errors path="countries[${entry.key}]" />
<div><input type="submit" /></div>

Comment by Zach Bailey [ 19/Feb/10 ]

This is a rather grievous bug since it affects ALL form tags that contain these bracketed paths, which we use extensively throughout our application. For us, this would be considered a blocker-level bug since there is no reasonable workaround.

Comment by Juergen Hoeller [ 20/Feb/10 ]

Ouch, that's a pretty bad regression that we unfortunately neither had a unit test nor an integration test for. Sorry for that - an unfortunate last-minute accident.

I've fixed this for 3.0.2 now. Should be available in tonight's 3.0.2 snapshot (build 591 and above).

FYI, 3.0.2 is scheduled for release in early March already. Please use a snapshot for the time being and let us know whether it works for you.


Comment by Zach Bailey [ 20/Feb/10 ]

Thanks for the quick turnaround, Juergen. I'll take a look at the snapshot and confirm the issue is fixed.

Comment by Hans Desmet [ 21/Feb/10 ]

Tried it out with 3.0.2 snapshot (build 592). Problem solved.

P.S. Problem in related SPR-6862 not yet solved

Comment by Grant Gochnauer [ 22/Feb/10 ]


Where can I find the nightly snapshot?


Comment by Grant Gochnauer [ 22/Feb/10 ]

Nevermind, I found it:

Comment by Grant Gochnauer [ 25/Feb/10 ]

There appears to be another issue with this:


It appears that indexed properties when used on the "id" attribute are still stripped.

Thus we would get something like:
<input id="promotionUser.formUserPropertyCodes'user_type'2" name="promotionUser.formUserPropertyCodes['user_type']" type="radio" value="543"/>

Notice how "ID" has the stripped brackets but the name attribute does not.

Comment by Zach Bailey [ 25/Feb/10 ]


While I am not a core spring developer I am confident that is intended behavior, because if you look at the HTML/XHTML spec you will see that id attributes cannot contain bracket characters.

Comment by Grant Gochnauer [ 25/Feb/10 ]


I suppose that is true but it does break backward compatibility with 3.0.0 in our environment against 3.0.2's fix.


Comment by Juergen Hoeller [ 25/Feb/10 ]

I'm afraid this is exactly what we desired to fix in 3.0.1 originally: the id attribute shouldn't contain any such brackets anymore, for no kind of input element. We were already doing this for all other form tags, just not for checkboxes and radiobuttons. It seems very much worth it to fix this remaining case once and for all in 3.0.x, with the name attribute regression properly addressed in 3.0.2, even we technically produce different ids for those then.


Comment by Grant Gochnauer [ 25/Feb/10 ]

Thanks for the quick response Juergen.

Comment by Spring Issuemaster [ 14/Jan/19 ]

The Spring Framework has migrated to GitHub Issues. This issue corresponds to spring-projects/spring-framework#11537.

Generated at Mon Feb 18 13:01:41 UTC 2019 using JIRA 7.9.2#79002-sha1:3bb15b68ecd99a30eb364c4c1a393359bcad6278.