Great! Fill free to post your comments here or in jira! 2014/1/20 [email protected] <[email protected]>: > That sounds exactly like the problem. Unless I was having completely > different backwards compatibility issues that were since fixed in 2.3.16, > the issue goes back a good bit further than described in the ticket from > what I have been seeing. I hope ya'll haven't been barking up the wrong > tree for it. I'll try and run some test cases around that ticket this week > and see what I come up with. > > > On Mon, Jan 20, 2014 at 3:26 AM, Lukasz Lenart <[email protected]>wrote: > >> Hi, >> >> I'm not sure if I understand your problem but maybe this issue is >> related to your problem >> https://issues.apache.org/jira/browse/WW-4257 >> >> 2014/1/20 [email protected] <[email protected]>: >> > I was running into some issues when updating to 2.3.16 (worms!) from >> around >> > 2.3.4.1 (2.3.14.1 also broke compat) in regards to implementing >> > ParameterNameAware. >> > >> > If you have a bean, "MyBean", with properties "id" and "name", when >> > implementing acceptableParameterName, before one needed only return true >> > for "myBeanInstance.id" and "myBeanInstance.name" - whereas now one needs >> > those along with "myBeanInstance", "id", and "name" for the action to >> > correctly populate the bean on an action. While I might have a funky >> > configuration involving Spring, the only change I made to experience the >> > break was updating the Struts2 libraries. >> > >> > I did not notice that documented or mentioned anywhere, so I thought I'd >> > pass the information along in case it did need to be documented or was a >> > bug. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >>
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
