There's got to be a better way of doing this than the way that I am doing it.
Convention plugin. According to my projects requirements error/validation/success messages are supposed to show on the jsp that generated them. So if I am on a page that adds a record and I leave all the fields blank, selecting submit will display some errors on that page but will not move on to a different page. All of these pages are in the /content dir so if I have: some-file.jsp and SomeFileAction.java and if SomeFileAction extends ActionSupport implements Preparable, then execute() is going to get called when ever the page is loaded even though it's empty and just returns "success"... I have to override and annotate execute with @SkipValidation to prevent messages from being displayed when the user has first loaded the page. The form on the some-file.jsp calls some-file!doSomething when the Submit button is selected. This turns things into a real mess. What the convention plugin does is consistent but not always predictable. I basically had to break with the conventions and use a few @Results and an additional action to get some predictability out of it. Anyway... how would you have done this? Jim C. --------------------------------------------------------------------- To unsubscribe, e-mail: user-unsubscr...@struts.apache.org For additional commands, e-mail: user-h...@struts.apache.org
