Re: Broken Compatibility issue with ParameterNameAware when upgrading

2014-03-28 Thread Lukasz Lenart
ave read and it seams, that i have to wait for version 2.3.17, right? > > regards, > Thomas > > > > > > > > -- > View this message in context: > http://struts.1045723.n5.nabble.com/Broken-Compatibility-issue-with-ParameterNameAware-when-upgrading-tp5715110p571560

Re: Broken Compatibility issue with ParameterNameAware when upgrading

2014-03-28 Thread thomas.hill
this message in context: http://struts.1045723.n5.nabble.com/Broken-Compatibility-issue-with-ParameterNameAware-when-upgrading-tp5715110p5715604.html Sent from the Struts - User mailing list archive at Nabble.com. - To unsubscribe, e

Re: Broken Compatibility issue with ParameterNameAware when upgrading

2014-03-28 Thread Lukasz Lenart
for param names (no using of dots)? > > regards, > Thomas > > > > -- > View this message in context: > http://struts.1045723.n5.nabble.com/Broken-Compatibility-issue-with-ParameterNameAware-when-upgrading-tp5715110p5715598.html > Sent from the Struts - User mailing

Re: Broken Compatibility issue with ParameterNameAware when upgrading

2014-03-28 Thread thomas.hill
n "session", "bean" and "firstname". Is this a bug or a feature? There are any restrictions for param names (no using of dots)? regards, Thomas -- View this message in context: http://struts.1045723.n5.nabble.com/Broken-Compatibility-issue-with-ParameterNameAware-wh

Re: Broken Compatibility issue with ParameterNameAware when upgrading

2014-01-20 Thread Lukasz Lenart
Great! Fill free to post your comments here or in jira! 2014/1/20 sma...@gmail.com : > 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 t

Re: Broken Compatibility issue with ParameterNameAware when upgrading

2014-01-20 Thread sma...@gmail.com
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

Re: Broken Compatibility issue with ParameterNameAware when upgrading

2014-01-20 Thread Lukasz Lenart
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 sma...@gmail.com : > 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

Broken Compatibility issue with ParameterNameAware when upgrading

2014-01-20 Thread sma...@gmail.com
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 tr