[ 
https://issues.apache.org/struts/browse/WW-1711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40223
 ] 

Rene Gielen commented on WW-1711:
---------------------------------

Sorry for breaking the build, I was pretty sure to have passed the tests before 
committing. In addition, I was unable to keep track last few days b/c some 
dealines hit me.
Stuarts fix looks really good, but after all I came to the opinion that his 
(and before my) fix are workarounds for an error happening much earlier in the 
template, when itemKey is assigned: why does this have to be a String? That 
question comes up if you look deeper into WW-1747. I am pretty confident that 
we will have a fix for both issues in a few minutes. I'll track this for 
WW-1747.

> select tag: current option is not selected if actual value to check is no 
> String (aka: nameValue resolves to type other than String)
> ------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WW-1711
>                 URL: https://issues.apache.org/struts/browse/WW-1711
>             Project: Struts 2
>          Issue Type: Bug
>          Components: Views
>    Affects Versions: 2.0.5
>            Reporter: Rene Gielen
>         Assigned To: Rainer Hermanns
>            Priority: Critical
>             Fix For: 2.0.6
>
>         Attachments: 1711-fix.patch, 1711-test.patch, 1711-testInt.patch, 
> Select-11.txt, Select-11.txt
>
>
> If the nameValue parameter for UIBean Components resolves to types other than 
> String, the correct value does not get selected.
> Example:
> <s:select label="%{getText('task.priority')}" name="task.priority.id" 
> value="%{task.priority.id.toString()}" list="priorities" listKey="id" 
> listValue="name" />
> If task.priority.id has type String, value gets seleted. If it a a Long (or 
> whatever), it does not get selected.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to