I added the documentation/comments for the new validator DTDs, but have a question:
Do we really want two DTDs? Orginally, there was just one configuration file, but we saw it would be convenient to have a master rules file and one or more files with the validations specific to an application. But the module-specific validations may also need to define custom validators that someone might want to add for a module, but not to the master set. So, if we have two, I'd suggest that there should be a validator-config DTD that defines everything and *maybe* a validator-rules-config DTD that omits the formsets. Also, the formset element does not declare the "variant" propery of the locale. David, is that supported? There also used to be a fieldOrder attribute to field, which I marked as :FIXME: in case it was just overlooked. <pipe-dream> Meanwhile, I can't help but wonder if there were some clever way we could define a single source file that could be used to generate the DTD and API documentation, or pluck out the API docs from the DTD, something like what is done with the tag libraries or with Java source files. Hmmmm, if we formatted them as JavaDocs is there something "out there" that would pluck them out for us? </pipe-dream> -T. -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
