Hi,
I would like to add something to this discussion since i'm the guy who
have reported WW-4154 <https://issues.apache.org/jira/browse/WW-4154>
Why && is obvious rather than ||
We have an Abstract Base Action class which contains some white listed and
black list parameter names, using *isAcceptableParam* we are handling it.
We are not handling or included any default struts2 black listed param name,
so we are leaving to strust2 to handle it. So in ParameterInterceptor first
strust2 default check will takes place (if successful &&) then
isAcceptableParam will check. Here there is no chance of checking same
parameter twice.
So according to me Strust2 default check is as equally important as custom
param check.
The problem with || is, if struts2 default check returns true then it will
never touch custom param check.
.
--
View this message in context:
http://struts.1045723.n5.nabble.com/Add-to-ParameterNameAware-JavaDoc-Warning-About-Using-tp5713285p5713568.html
Sent from the Struts - Dev mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
