DO NOT REPLY [Bug 1300] - test coming on on stdout on Transformer.transform() encountering a TransformerException

[bu...@apache.org]

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1300>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=1300

test coming on on stdout on Transformer.transform() encountering a TransformerException

curcuru@apache.org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Priority|Medium                      |Low



------- Additional Comments From curcuru@apache.org  2001-10-05 08:26 -------
There are two parts to this question (in my mind, anyway):
-- Cleanup and better definition of the format of all error messages.  We know 
there's more work to be done to ensure all our exceptions are clear and hold 
all the info a user would need to debug problems - like including line/col 
information in the exception easily.
-- Use of System.out/.err throughout the product.  Obviously the command line 
tool should put status, etc. info to the console, but it's not always clear 
what the best decision is for the guts of the transformer to do.  I.e. some 
users who stick Xalan in the middle of a server might never need to see us 
dumping info to the console, since the console is never read.  We don't 
necessarily have a specific policy for all cases on this yet.
Unfortunately since we do report the bulk of errors thoroughly in some manner, 
this is of a lower priority than many other current bugs.