Rather than create my OD configs manually, I use my own objects and methods to create OD configs on the fly in my workflows. In one case, I was creating a config file with a missing "/" to end a tag, and so the config was invalid. However, when I ran iwodstart for that config, I received no feedback anywhere that the XML was invalid. Only when I pulled up the OD Admin GUI on that config was I able to see that it was invalid. Why does iwodstart not report somewhere that the XML is malformed? It should tell me in the otherwise useless set of information that iwodstart returns. The OD Admin GUI should not be the only place that reports malformed configs.
Dave SmithSr. Software Engineer
Nike, Inc.
(503) 671-4238
DavidH.Smith@nike.com
