[
https://issues.apache.org/jira/browse/WW-4401?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14121714#comment-14121714
]
Sravanthi Bobba edited comment on WW-4401 at 9/4/14 6:26 PM:
-------------------------------------------------------------
Right now we are using older version of struts and trying to upgrade to the
newer version and suddenly things start to break because of the assumption that
the values are null on no selections. Not a problem to fix the entire project
not to look for null. Not sure if it was an intentional behavior. Is there an
easy way to find out these kind of changes, I couldn't find this change in the
release notes. Were there any other changes to Collections and Variables too
regarding the default populations. Thanks for the help
was (Author: sbobba):
Right now we are using older version of struts and trying to upgrade to the
newer version and suddenly things start to break because of the assumption that
the values are null on no selections. Not a problem to fix the entire project
not to look for null. Not sure if it was an intentional behavior. Is there a
way to find out these kind of changes, I couldn't find this change in the
release notes. Were there any other changes to Collections and Variables too
regarding the default populations. Thanks for the help
> <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)
