Good point on the blocking of the action for actionErrors.
..trying to track down a strange validator error, it stops working and I have to log out and back in again to get it working. It starts with session timeout error, possibly related to a npe in a <field-validator type="fieldexpression"> / expression, <s:token /> or something else. :-(.
Cheers Greg On 09/05/2021 09:34, Yasser Zamani wrote:
I remember if I'm not wrong Struts won't execute action when it has validation errors. Maybe that's the case here where Struts doesn't want to block action execution and merely wants to inform developer? But anyway personally I think you're right, we should either change LOG.error to LOG.warn or use actionErrors. Regards. On 5/6/2021 2:05 PM, Greg Huber wrote:In the ParametersInterceptor there is a method protected void notifyDeveloperParameterException{..} which logs developer stuff : LOG.error(developerNotification); if (action instanceof ValidationAware) { // see https://issues.apache.org/jira/browse/WW-4066 Collection<String> messages = ((ValidationAware) action).getActionMessages(); messages.add(message); ((ValidationAware) action).setActionMessages(messages); } It logs to the log file as an error, but sets it as actionMessages for the UI, should this be actionErrors? For me actionMessages are for success, whilst actionErrors are errors to do something.--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
