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=21025>. 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=21025 DOMException code 14 when transforming to Xerces DOM ------- Additional Comments From [EMAIL PROTECTED] 2003-06-24 06:43 ------- OK. It is definitely a DOMException that is being thrown - I've added a catch handler for XalanDOMException BEFORE that for DOMException (as far as I can tell, there is no inheritance relationship, but I wanted to make sure), but that handler is not invoked. I note that in XalanTransformer.cpp, there are NO catch handlers for DOMException, so I guess you are relying on catching them at some other level. Anyway, I am attaching the header file that contains all my C++ code for invoking Xalan. If you search for FormatterToXercesDOM, you will find a declaration for it in the member function transform_to_DOM. This function sets up the formatter and then calls the member function transform(), which just selects which from of XalanTransformer::transform to invoke. This code works in other circumstances (i.e. those that do not produce a code 14 exception, I guess). The exception handlers, however, were added purely for debugging this problem, as the documentation for XalanTransformer::Transform() does not mention any exceptions that might leak. I would like to know which exceptions may legitimately be thrown.
