[eluser]Scriptor[/eluser]
I think the User Guide validation example has it so that the form submits it to the original controller method, but that might have been done just to keep things short. The validation library should work either way (as long as you put the validation-specific code in the right method, of course).
Using the same method has the advantage that the user's URL doesn't change if the form's data isn't accepted. Since you're using the same method you just have to tell it to load the view, but this time show the errors.
On the other hand, having one giant method that handles both presenting the form, and processing it, would be very bulky and prone to bugs. A separate method would leave you free to separate the code, an added benefit is that no unnecessary validation/processing would be run when the user first loads the form.
A solution would be to use another method (customer/save), then if validation fails saving the error data somewhere (flashdata or sessions) and redirecting back to customer/add, which would show the form with the errors.
