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=22145>. 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=22145 page attribute in the Validation Config file ------- Additional Comments From [EMAIL PROTECTED] 2003-08-18 17:12 ------- The above attachments are my proposal for adding this new functionality of pages instead of page on fields: 7874: Field.java I added an int[] pages field with getPages(), setPages(String pages), and containsPage(int page) methods. It is backwards compatible with getPage() and setPage(int page) using index 0 of the int[]. The containsPage(int page) method checks through the int[] to see if page is there. The pages field still defaults to one page of 0 like the old page field did. This means that you can still use the page attribute in your validation config file for a field with one page, but you can use the pages attribute with comma-seperated pages to be used by more than one page. 7875: Validator.java The Validator uses the new containsPage(int page) method in Field to check if the forms page is found in the Fields pages int[]. Before, it checked if the form page was <= the Field's page, but now it the form page must be in the Field's pages. 7876: validator_1_1.dtd Added pages attribute to the field element. 7878: Added call to Field.containsPage(int page) to check if the form's page exists in the field's pages. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
