Re: AliasInterceptor parameter mapping issue

Thanks for the response, Yasser! Sure thing, I've created the bug here: https://issues.apache.org/jira/browse/WW-5087 Best, Brian On Fri, Aug 28, 2020 at 8:56 AM Yasser Zamani wrote: > Hi Brian, > > Sorry for inconvenience :( yes for me as well it looks like an > unintentional bug introduced

Re: AliasInterceptor parameter mapping issue

Hi Brian, Sorry for inconvenience :( yes for me as well it looks like an unintentional bug introduced by [1]. Thanks a lot for writing to us! To followup its resolution would you mind create a new JIRA ticket? Regards. [1] https://github.com/apache/struts/commit/787f2f96eb9f1bb3c8012ab42a

AliasInterceptor parameter mapping issue

Hello, We are running into an issue with the AliasInterceptor after upgrading to 2.5.22 (from 2.3.35). The issue is that the fallback behavior to look in HttpParameters for a value guarantees a value will always be set and that Evaluated.isDefined() will subsequently always return true. The issue