Consider the following: You have a new user creation form, and need to ensure that the username chosen doesn't already exist in the database.
To keep any business logic out of the ActionForm, you'd really like to do this in the Action. However, as near as I can tell, the Action doesn't have any access to the ActionErrors returned from the form, which means that you'd have to use another mechanism (like a request attribute) to return these type of errors. Am I missing something, or is this the best practice for business logic validation of forms? James -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
