Affects Version/s: 2.5.5
Fix Version/s: 2.5.8
If an action has a List parameter, but is only called with one value, the parameter is never set.
Consider the basic action below.
Performing a GET on "/test.action?object.field=a"
Expected outcome: "object" list should be populated with 1 object. with a field value of "a"
Actual Outcome: object list is empty.
Performing a GET on "/test.action?object.field=a&object.field=b" works as expected (list has 2 entries).
The following changes to ParametersInterceptor break this behavior. because XWorkListPropertyAccessor Expects an Array of strings for value (which was previously sent when HttpParameters was a map instead of an Object).