Re: Request parameters need corresponding getters/setters in action?

2014-03-28 Thread Manuel López Blasi
Sorry i mistaken version, i'm upgrading from 2.1.8.1 to 2.3.16.1 , it was late and i was a little dizzy. About setter issue it's good to hear is just a warning. I'll wait for next version for datetimepicker. Thanks a lot, Cheerz. El 27/03/2014 17:49, Lukasz Lenart escribió: 2014-03-27 21:41 GM

Re: Broken Compatibility issue with ParameterNameAware when upgrading

2014-03-28 Thread Lukasz Lenart
Yes, hope in next week ;-) 2014-03-28 9:34 GMT+01:00 thomas.hill : > Hi, > > sorry for duplicate, i thought i had deleted the first post. > > I would migrate from version 2.3.15.3 to 2.3.16.1 > I did not read the issue because the system was in maintenance, but now i > have read and it seams, that

Re: Broken Compatibility issue with ParameterNameAware when upgrading

2014-03-28 Thread thomas.hill
Hi, sorry for duplicate, i thought i had deleted the first post. I would migrate from version 2.3.15.3 to 2.3.16.1 I did not read the issue because the system was in maintenance, but now i have read and it seams, that i have to wait for version 2.3.17, right? regards, Thomas -- View this

Re: Broken Compatibility issue with ParameterNameAware when upgrading

2014-03-28 Thread Lukasz Lenart
Have you followed the link of the issue? From what version do you migrate to 2.3.16? 2014-03-28 8:30 GMT+01:00 thomas.hill : > Hello, > > i have the same problem. > Since version 2.3.16 (and 2.3.16.1 too) a lot of my parameters will not > accepted. > I have a lot of paramNames with a dot in name l

Re: Broken Compatibility issue with ParameterNameAware when upgrading

2014-03-28 Thread thomas.hill
Hello, i have the same problem. Since version 2.3.16 (and 2.3.16.1 too) a lot of my parameters will not accepted. I have a lot of paramNames with a dot in name like "session.bean.firstname" and this doesnt work. It seams so, that the ParametersInterceptor split these paramNames in "session", "bean