[
https://issues.apache.org/jira/browse/WW-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14122535#comment-14122535
]
Lukasz Lenart commented on WW-4401:
-----------------------------------
To read about changes in given version read Version Notes, eg.
http://struts.apache.org/release/2.3.x/docs/version-notes-2316.html but when
you migrate from very old version (2.1.x branch is old, I'd say very old) you
must read each Version Notes, step by step.
I'm not sure if WW-3603 was the change I thought of - it rather eliminates your
issue. Anyway, basing on {{null}} isn't a good idea because you simple don't
know if values wasn't sent (via request) or it was set to empty value
({{?myParam=}}). Even if user didn't select a value, web browser will post an
empty value. And memory isn't an issue here at all - it's far better to create
short-living objects then long-living one - garbage collector is your friend :-)
And I'm wondering how it is possible to not select value when you use
{code:xml}
<s:select list="xyzlist" name="bean.someArray"></s:select>
{code}
in such case, the first element of the list will be selected by default.
> <s:select list="xyzlist" name="bean.someArray"></s:select> , if no selections
> made by user, the array gets injected with empty array instead of null and
> same is the case with List
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: WW-4401
> URL: https://issues.apache.org/jira/browse/WW-4401
> Project: Struts 2
> Issue Type: Bug
> Components: Plugin - Tags
> Affects Versions: 2.3.16.3
> Environment: Mac, Tomcat 6/7
> Reporter: Sravanthi Bobba
> Fix For: 2.5.x
>
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
