What about a schema like this. -xml {path} -xsl {path} -html {path}
This seems like a pretty good approach. Why don't you give it a go, and see how it works out in practice? I was wondering, though: can we perhaps embed our "default" XSL stylesheet, or possibly even several potential alternate XSL stylesheets, into the derbytools.jar archive directly, so that the user doesn't need to manage this extra moving part for the simple case of being willing to use our default XSL stylesheet as is? thanks, bryan
