Feature request - possibility to use the validate and noDirectives arguments combined

Jun 25, 2009 at 11:23 AM

Hi,

The validate argument currently will return an error if any substitution settings are undefined or if the result document is not well-formed.

This means that validate will always fail, when using XmlPreprocess on a file which is not XML. We would however very much like to be able to get an error if any substitution setting can not be found, as it would enable us to catch these errors at deployment time, as opposed to run time.

Thanks

 

Coordinator
Jun 30, 2009 at 3:04 PM

Ouch, yes, I didn't think of that combination.  What would you suggest we do?  Add another argument to tell it not bypass the check for well-formedness?

Jul 1, 2009 at 8:36 AM

I suggest to add arguments like this:

/validateSubstitions         Validate substitutions, return an error if any
                          substitution settings are undefined.

/validateXml         (/v) Validate XML, return an error if the result
                          document is not well-formed.

/validate         (/v) Validate settings. Turns on the following validations:
                            /validateXml
                            /validateSubstitions

This would also enable to only test for well-formedness, if someone would wish that. Furthermore it opens up for future validations.

An alternative is to let noDirectives imply not to test for well-formedness. This can not be recommended however, because using noDirectives with xml-files are perfectly fine.