DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26485>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=26485 automate maxlength validations ------- Additional Comments From [EMAIL PROTECTED] 2004-01-28 15:25 ------- In this case, I think rather than a patch, it would be clearer to create new classes implementing this behavior. I agree with James that if you set about implementing it, you may find yourself struggling under the weight of the alternate scenarios. Also, if you have separations between your view (forms) and your model, then hard-coding maximum lengths into java classes seems like a liability greater than the effort of copy/pasting the last maxlength block you had in validator-rules for a new field. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
