sax

First off, let me say I am a new to SAX and Java. I am trying to read information from an XML file that is not well formed. When I try to use the SAX or DOM Parser I get the following error in response: The markup in the document following the root element must be well-formed. This is how I set up my XML file: <format type="filename" t="13241">0;W650;004;AG-Erzgeb</format> <format type="driver" t="123412">001;023</format> ... Can I force the SAX or DOM to parse XML files even if they are not well formed XML? Thank you for your help. Much appreciated. Haythem Your best bet is to make the XML

Is it feasible in Java using the SAX api to parse a list of XML fragments with no root element from a stream input? I tried parsing such an XML but got a org.xml.sax.SAXParseException: The markup in the document following the root element must be well-formed. before even the endDocument event was fired. I would like not to settle with obvious but clumsy solutions as "Pre-append a custom root element or Use buffered fragment parsing". I am using the standard SAX API of Java 1.6. The SAX factory had setValidating(false) in case anyone wondered. npe First, and most important of all, the content

I have some XML that I'm parsing with a SAX parser in Java. It starts with this preamble: <!DOCTYPE math PUBLIC "-//W3C//DTD MathML 3.0//EN" "http://www.w3.org/Math/DTD/mathml3/mathml3.dtd"> How do I change this to use a local DTD? I suppose I could do something like this: <!DOCTYPE math PUBLIC "-//W3C//DTD MathML 3.0//EN" "file:///c:/MathML/mathml3.dtd"> Not exactly like that, but something like that. However, I need the path to be independent of the user's system. How do I use a local DTD with a path relative to the class path? Take a look at this article on using XML catalogs to resolve

When trying to parse incorrect XML with a character reference such as &#x1 , Java's SAX Parser dies a horrible death with a fatal error such as org.xml.sax.SAXParseException: Character reference "&#x1" is an invalid XML character. Is there any way around this? Will I have to clean up the XML file before I hand it off to the SAX Parser? If so, is there an elegant way of going about this? Use XML 1.1! skaffman is completely right, but you can just stick <?xml version="1.1"?> on the top of your files and you'll be in good shape. If you're dealing with streams, write a wrapper that rewrites or

I've a BufferedInputStream from which I want to parse XML with SAXParser but then reuse it again (eg. mark(int) & reset() ). However this stream is closed in parse() method. Is it possible to somehow tell SAXParser to leave it open? The last resort is to wrap this stream with un-closeable stream. Thank you. How about something like: class WontCloseBufferedInputStream extends BufferedInputStream { public void close () { // Do nothing. } public void reallyClose() { super.close (); } } You can pass InputSource object rather than InputStream object to SAXParser sample code SAXParser parser = //

I have an XML Schema which contains a number of <any namespace="##other" processContents="lax" minOccurs="0" maxOccurs="unbounded" /> definitions, i.e., it allows to insert arbitrary tags of other namespaces. processContents="lax" indicates that the parser should try do validate these tags, if it has the according schema (1) (2) . For me this means, that if I give the parser all schema documents, and there is an invalid XML tag of one of the secondary namespaces, it needs to report an error. However, it seems that the Java XML validator ignores such errors. I have verified that the parser has

I need to parse potentially huge XML files, so I guess this rules out DOM parsers. Is out there any good lightweight SAX parser for C++, comparable with TinyXML on footprint? The structure of XML is very simple, no advanced things like namespaces and DTDs are needed. Just elements, attributes and cdata. I know about Xerces, but its sheer size of over 50mb gives me shivers. Thanks! If you are using C, then you can use LibXML from the Gnome project. You can choose from DOM and SAX interfaces to your document, plus lots of additional features that have been developed over years. If you really