Re: Iusse in BigDecimal conversion after upgrading from 2.5.10.1 to 2.5.13

2017-10-04 Thread sreekanth
thanks Yasser for all you help and code. I would like to conclude this as a struts2 upgrade change, as BigDecimal field value was setting as BigDecimal.ZERO when field value passed as empty in struts2.5.10.x or < whereas 2.5.13 will set such empty BigDecimal field as null value (that is the correc

Re: How to share tiles while using both struts 1 and struts 2 during migration?

2017-10-04 Thread Lukasz Lenart
2017-10-03 20:31 GMT+02:00 ss2...@cornell.edu : > Hello, > > I have a struts app which uses both struts 1 and struts 2. While we are > migrating slowly and trying to remove all struts 1 stuff, we want to share > tiles during the migration process across both s1 and s2. While there is > enough do

Re: Iusse in BigDecimal conversion after upgrading from 2.5.10.1 to 2.5.13

2017-10-04 Thread Lukasz Lenart
2017-10-04 12:41 GMT+02:00 Yasser Zamani : >> 2.5.13. But now I also tested 2.5.10.1 and get following warn when try >> to set empty string value to a BigDecimal: >> >> Unexpected Exception caught setting 'myList[0].crAmt' on 'class >> me.zamani.yasser.ww_convention.actions.MyBigDecimalList: Error

Re: Iusse in BigDecimal conversion after upgrading from 2.5.10.1 to 2.5.13

2017-10-04 Thread Yasser Zamani
On 10/4/2017 10:45 AM, sreekanth wrote: > thanks Yasser, let me setup a sample too. I already went through fixes > introduced at WW-4581 as well and ran a test against it and found that's not > the reason for this behavior rather something related to form field binding. > > Here i'm adding your

Re: Iusse in BigDecimal conversion after upgrading from 2.5.10.1 to 2.5.13

2017-10-04 Thread sreekanth
thanks Yasser, let me setup a sample too. I already went through fixes introduced at WW-4581 as well and ran a test against it and found that's not the reason for this behavior rather something related to form field binding. Here i'm adding your finding which i too believe the root cause for this