The answer to your first question is a qualified "yes." Qualified because
I don't think it's ever been tested, so it's hard to say. Since the
proxies must obey the interfaces, it should be OK. We used to use the
Xalan source tree for the source and proxied Xerces nodes for result tree
fragments, and that worked as expected, but it's been a while since we've
done that. I'd say go ahead and experiment, and we'll fix any problems
that might arise.
The answer to your second question is most likely yes, but I'd more details
before I give a more definitive answer. At the library level, Xalan is
designed to handle any sort of exception at any time. In fact, there are
very few try/catch blocks in the code. The basic philosophy is that any
call could throw any exception, so always be prepared, or write the code in
such a way that stack-unwinding as a result of an exception is treated the
same way as stack-unwinding as the normal course of execution.
Now, at the application level, the Xalan and testXSLT executables are not
necessarily designed to handle any sort of exception that might come along.
But that's an application issue, and not a Xalan issue.
Dave
"Brian Quinlan"
<brian@sweetapp. To: <[EMAIL PROTECTED]>
com> cc:
Subject: XalanDOM/Nodesets and
exceptions
12/20/2001 02:06
AM
Please respond
to xalan-dev
I have two questions about valid behavior for Xalan extensions (both for
functions and for DOMs):
1. can a nodeset contain notes from any XalanDOM i.e. can I mix and
match proxies Xerces nodes, Xalan nodes and proxied nodes from 3rd party
DOMs?
2. is Xalan designed such that any node method can safely throw any
exception? or could bad things happen?
Cheers,
Brian
