You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xalan.apache.org by Da...@lotus.com on 2001/02/15 01:09:37 UTC
Re: SAX && namespaces (Xalan C++ 1.0)
Yes, I rounded out the implementation SAX2 and gave the code to the Xerces
team. It was release in Xerces 1.4, which is what we're release Xalan-C++
1.1 against.
Is there any reason why you included that previous message from the list in
your post? I can't figure out if it's somehow significant, or just spam.
Dave
"David
Curley" To: <xa...@xml.apache.org>
<dcurley@obli cc: (bcc: David N Bertoni/CAM/Lotus)
x.com> Subject: SAX && namespaces (Xalan C++ 1.0)
02/15/2001
06:59 PM
Please
respond to
xalan-dev
Can anyone tell me if namespaces will work with SAX in the
upcoming release of Xalan C++ ? I'd hate to have to switch
to using the DOMParser just for this, and especially if it's
likely to be fixed soon.
RE: SAX && namespaces (Xalan C++ 1.0)
Posted by David Curley <dc...@oblix.com>.
Thanks Dave. Just to clarify, are you only saying that
you made it *possible* to do this with Xerces 1.4, or
that Xalan 1.1 actually takes advantage of it CreateSAXParser ?
Dave.
(P.S. Your luncheon meat analysis was on the mark.
I guess I hit reply instead of new. Sorry... )
-----Original Message-----
From: David_N_Bertoni@lotus.com [mailto:David_N_Bertoni@lotus.com]
Sent: Wednesday, February 14, 2001 4:10 PM
To: xalan-dev@xml.apache.org
Subject: Re: SAX && namespaces (Xalan C++ 1.0)
Yes, I rounded out the implementation SAX2 and gave the code to the Xerces
team. It was release in Xerces 1.4, which is what we're release Xalan-C++
1.1 against.
Is there any reason why you included that previous message from the list in
your post? I can't figure out if it's somehow significant, or just spam.
Dave
Halting the interpreter
Posted by Brian Quinlan <Br...@ActiveState.com>.
Hi,
I am using Xalan-C 1.0 and was wondering if there is a structured way to
halt the interpreter. Right now I am implementing a TraceListener and
throwing an exception inside of it to stop the interpreter. Is there a
better way to do it? Ideally, I would get an exception at the level of the
Stylesheet "process" method call with no error messages.
Thanks.