Kimbro Staken wrote:
Looks ok to me, SAXEventGenerator is used by IndexManager too but it doesn' t bother with the return value anyway.
Thanks for committing that (and the NodeImpl patch).
The situation it better now, but given the the XMLDBException class has no notion of a "cause" or "nested" Throwable[0], any SAXExceptions thrown still can't be examined by the client API's user.
As a workaround in my local tree, I've moved the call to org.apache.xindice.Debug.printStackTrace() that was in SAXEventGenerator.start() to XMLResourceImpl, so any SAXExceptions will still at least get dumped to stdout (or where ever the Debug class is pointing to at the time).
Tiny patch attached. This may want to make it's way into the tree, at least until a better solution is found.
Mike.
[0] - does anyone know if this limitation is going to get fixed in a latter release of the XMLDB API?
-- Mike Gratton <[EMAIL PROTECTED]> "Every motive escalate." Blatant self-promotion: <http://web.vee.net/>
Index: java/src/org/apache/xindice/client/xmldb/resources/XMLResourceImpl.java
===================================================================
RCS file:
/home/cvspublic/xml-xindice/java/src/org/apache/xindice/client/xmldb/resources/XMLResourceImpl.java,v
retrieving revision 1.1.1.1
diff -u -r1.1.1.1 XMLResourceImpl.java
--- java/src/org/apache/xindice/client/xmldb/resources/XMLResourceImpl.java
6 Dec 2001 19:33:54 -0000 1.1.1.1
+++ java/src/org/apache/xindice/client/xmldb/resources/XMLResourceImpl.java
23 Feb 2002 03:02:52 -0000
@@ -333,6 +333,7 @@
}
}
catch (Exception e) {
+ org.apache.xindice.Debug.printStackTrace(e);
throw FaultCodes.createXMLDBException(e);
}
}
