On Mon, February 14, 2005 2:28 pm, Don Brown said: > - First level validation would be handled through commons-validator as > we do now. Second level, the one where validate() code would be another > specified method, defined in the action mapping or method annotation.
This point made me think of something... What about the idea of adding the concept of an <action-bean> in struts-config? Instead of having a bunch of new attributes to an <action> mapping, what if you instead define an <action-bean>, just like you define a <form-bean> today, that declares what your validate method is, what your primary execute() method is (if defined you treat it like a "classic" Action), maybe what chain it should use (where Don I think was asking how to figure out what process-* chain should be used), whatever else everyone thinks we need. Then, in your <action> mappings, you simply reference the appropriate <action-bean> entry, just like <form-bean>'s are. That might make for a nice separation, and also would allow multiple <action> mappings to share the same Actions configured in the same way, and all of this is done without potentially duplicating a lot of information in each <action> mapping, especially when multiple mappings use the same Action. -- Frank W. Zammetti Founder and Chief Software Architect Omnytex Technologies http://www.omnytex.com --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
