form:select 3.0.1 regression bug when binding to a map [SPR-7040]

[spring-projects-issues]

Jeff Johnston opened SPR-7040 and commented

I found a bug that surfaced in Spring 3.0.1. The problem is with binding a value to a map with the form select tag.

In my JSP I have the following select tag. This will bind to a Map<String, String> field in my command object.

<form:select path="questions[${question.key}]" cssClass="${question.key}" items="${question.answers}" itemValue="key" itemLabel="name"/>

If I do a view source I can clearly see the problem.

In Spring 3.0 I have this:

<select id="questionsARTISAN_ARMOIRE_WOOD" name="questions[ARTISAN_ARMOIRE_WOOD]" class="ARTISAN_ARMOIRE_WOOD"><option value="001" selected="selected">Cherry</option><option value="002">Walnut</option></select>

In Spring 3.0.1 I have this:

<select id="questionsARTISAN_ARMOIRE_WOOD" name="questionsARTISAN_ARMOIRE_WOOD" class="ARTISAN_ARMOIRE_WOOD"><option value="001" selected="selected">Cherry</option><option value="002">Walnut</option></select>

Notice how the name is "questionsARTISAN_ARMOIRE_WOOD" instead of "questions[ARTISAN_ARMOIRE_WOOD]". The brackets got dropped in 3.0.1.

---

Affects: 3.0.1

Issue Links:

• Spring MVC regression: binding to indexed properties is broken [SPR-6871] #11537 Spring MVC regression: binding to indexed properties is broken ("duplicates")

[spring-projects-issues]

Juergen Hoeller commented

This is an unfortunate regression in 3.0.1 which has been fixed in recent 3.0.2 snapshots already. Feel free to give 3.0.2 early try; it's scheduled for release next week.

Juergen