David Newton wrote:That's *one* way to do it--is it the "right" way? Depends. I tend to cluster classes by application functionality, which is independent of the view technology.
Thanks for your answer. I can see the advantages in keeping everything associated with one application functionality together.
Another question, but still on the topic. I saw that you were proficient in
Struts so maybe this can be generalized to any MVC framework: When using AJAX calls, how do you give feedback for illegal input, that is form:error and such? If it's a simple textbox it's easy but what about input in an complex datagrid for instance? Do you write your own tags for it or use the ones provided by the framework? Perhaps setting my own error attributes is an option, that is, not using the MVC framework for error handling at all. But it seems as a waste of time to reimplement something that already exists.
In short: Is there some general solution to the problem of validating complex AJAX widgets?