Andy Clark wrote:
> David Walend wrote:
> > Once Xerces starts a parse, can it be stopped? How?
>
> Throw a SAXException from your registered handler.
Late last night, I decided to throw a subclass of SAXException named
SAXInterruptedException. (I've been assuming SAXExceptions were
relatively d
Elena Litani wrote:
> Hmmm.. We do plan to implement DOM L3 specs and although we did not
> discuss implementing Abstract Schema [AS] module (that allows editing
> and querying grammars), the APIs are there. Do we want to provide
> another way to access grammar??
Are you confident that the DOM L3
[EMAIL PROTECTED] wrote:
> In SGML it is a common and well proven technic only to use the PUBLIC
> identifier to reference the grammar.
I know my opinion is contradictory with SGML users but I
think that the public identifier is redundant and ultimately
not very useful. You can alias external ent
[EMAIL PROTECTED] wrote:
> But may be that you are able to standardize the framework you
> want to build.
There's not much need to. There are already suitable interfaces
to do most things. We're building a framework for the parser
implementation that is flexible enough for power users to do
very
David Walend wrote:
> Once Xerces starts a parse, can it be stopped? How?
Throw a SAXException from your registered handler.
Alternatively, if you want to drive the parser yourself,
it can operate in pull-parser mode. In that way, you're
only parsing as much as you need anyway.
--
Andy Clark *
Write to a file:
OutputFormat format = new OutputFormat(aDoc);
format.setIndenting(true);
FileOutputStream fOut = new FileOutputStream(aFilename);
OutputStreamWriter writer = new OutputStreamWriter(fOut, "UTF-8");
XMLSerializerserial = new XMLSeria
Hi all,
In Xerces-1_4_0, there's do have a grammar-access
feature. I think in this way can validate DOM tree
dynamicly, but I don't know how to use them after
setfeature.
If there's an example that would be much help!!!
Thanks a lot!
Annie.
__
I tried asking this question on the user's list with no luck.
I've a project which involves parsing very large documents inside a user
interface. I'm using a
SAXParser.
I'd like to be able to stop the parse by calling parsingThread.interrupt() from
another thread. I've crawled the Xerces 1.4.1
>Hmmm.. We do plan to implement DOM L3 specs and although we did not
>discuss implementing Abstract Schema [AS] module (that allows editing
>and querying grammars), the APIs are there. Do we want to provide
>another way to access grammar??
>I am not sure how DTDContentModelHandler is useful for ed
Hi,
I had the same problem but I figured it out and now it works fine:
What parser do you use ?
import org.xml.sax.helpers.*;
import org.xml.sax.*;
import org.apache.xerces.parsers.SAXParser;
import org.apache.xerces.readers.*;
import javax.xml.parsers.DocumentBuilder;
import com.netcs.runtime.
Hi there,
Could some one please tell me how I can
- save my DOMDocument to file
- write the entire DOMDocument to a string
In the MSXML parser their exist to methods on the DOMDocument to take care
of this:
. save() and .xml()
What is the familiar methods in the Xerces parser?
I hope some one
Hi
I hava a problem when parsing an InputSource with SAX and Xerces.
when I'm parsing a file by giving its name, it's working fine:
Parser parser = ParserFactory.makeParser(parserName);
parser.setDocumentHandler(counter);
parser.setErrorHandler(counter);
Andy Clark wrote:
> [1] DTD Handler Interfaces
> I'm now leaning towards Glenn's earlier suggestion that we
> can provide DTD information needed to DTD editor writers
> (arguably a very small percentage of the parser user base)
> via the SAX xml-string property. I'm not suggesting that
> we *will
13 matches
Mail list logo
