ProblemListener

[maX Ekstrom <me...@dmind.com>]

Registering a custom ProblemListener with the XercesLiaison should override 
any behavior of the default problem listener, but from my limited tests, it 
is still producing output on System.err.

In an attempt to work around this, I circumvented the XSLTProcessorFactory, 
and created my own XercesLiaison with a custom ErrorHandler. This did, in 
fact, allow me to control the output of error messages, but to my dismay, I 
lost all the "value-add" features of the ProblemListener and its greater 
precision in tracking error origins. It seems that supplying one's own 
ErrorHandler supercedes the ProblemListener.

There must be something I am missing. In writing my own ProblemListener, I 
found its role to be slightly ambiguous. For example, there is no 
explanation for why the the interface should call for two methods with 
nearly identical purposes: message and problem. Why should the message 
method, with its limited diagnostic capacities, be necessary at all?

If there are known issues relating to the ProblemListener's behavior, I 
will happily contribute to the project to this end. If there is something I 
am overlooking or just generally ignorant of, I welcome clarification.

Needless to say, I'm impressed with the project so far.

-maX
_________________________________________________
Dmind Corporation
maX Ekstrom
Applications Architect
161 Maiden Lane
3rd Floor
New York, NY 10038
(212) 487-7400 Ext. 228
(212) 487-7408