Hmm - some of your points sound very good, but something about this makes me think you might want to 'think outside the box' and consider approaching it from another direction.
For example, instead of writing complex stylesheets or implementing custom tracing or debugging code to watch the xml get processed, why not just write a schema or DTD and tell the parser to validate the xml doc before it's processed? This will be much more robust and easier to maintain. If you want some code that exercises part of the tracing API's in Xalan, you can look at xml-xalan/test/java/src/org/apache/qetest/xalanj2 for TraceListenerTest and TransformStateAPITest/TransformStateTest, which are a couple of the available test scripts for the tracing functionality. Note that they are not necessarily documented for end-users, and they do *not* necessarily represent the best way to use tracing (since they may occasionally have negative tests in there). - Shane ===== <eof aka="mailto:[EMAIL PROTECTED]" "http://www.otnemem.com/"=.sig /> __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com
