DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=27870>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=27870 validator & inheritance ------- Additional Comments From [EMAIL PROTECTED] 2004-03-23 15:16 ------- I didn't follow exactly the Tiles pattern as it would imply quite a few more changes. I believe solving inheritance is naturally part of the process method anyway. I don't know if it would be interesting to reference the parent form. For this purpose I didn't find it useful, but it might be useful in the future. It would probably be wise not to use process(Map, Map) at all in case it may get deprecated (just guessing). A couple of issues: 1. Should it throw an exception: throw new ValidatorException("Error while resolving form definition inheritance: child '" + getName() + "' can't find its ancestor '" + getExtends() + "'. Please check your validation definition file."); if its parent form is not found? The thing is that it should go all the way up to ValidatorResources.initialize... 2. It would probably be interesting to have a notation similar to the one in the attribte depends (comma delimited), making it possible to extend from multiple forms. What do you think? PD: I don't know if the dtd that I applied the patch to was correct (validator_1_1_2) --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
