Thanks Maurizio. I understand this kind of expression is not recommended for security reasons, and this is probably a good thing if such expressions were not evalued by default.
But it appears that such expression IS evalued, the setter is invoked with the correct value. That's why I think there is something wrong somewhere: - if such expression shouldn't be allowed, then the setter shouldn't be called at all (otherwise it means that security is broken) - if such expression are allowed, then I don't understand the field error (xwork.default.invalid.fieldvalue) (I tested this on Struts 2.3.1.2 but will upgrade to 2.3.4 soon) -- View this message in context: http://struts.1045723.n5.nabble.com/ParamsInterceptor-is-input-bean-getFoo-bar-name-supposed-to-work-tp5710056p5710060.html Sent from the Struts - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
