I'm currently tossing around the idea of a XWork sanity checker. I'm guessing something that runs as an ant task and checks a lot of the things that have bit us in the ass during development.

Here are some examples of questions I want it to answer:

Do all the actions exist?
Do all the interceptors exist?
Do actions have a setter for a component, but not implement it's enabler in the class definition?
Do actions have a getter for every setter and vice-versa?


There are others, but I can't think of them right now. As you can see, this sanity checker won't be definitive, i.e. can't be part of your test suite, but it could be very handy in tracking down weird behavior. The third and the fourth questions are little things that we've spent quite some time tracking down only to slap our foreheads when we catch it.

Please email me any other common gotchas that I could include in this.

Anoop



-------------------------------------------------------
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your skills.  Sign up for IBM's
Free Linux Tutorials.  Learn everything from the bash shell to sys admin.
Click now! http://ads.osdn.com/?ad_id=1278&alloc_id=3371&op=click
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork

Reply via email to