DOM problem

HI! I´m not really sure if this is the place to post this question... but i´m having a little problem here and I need some help I have a voucher.xml file wich is a ´template´ to create new xml voucher representations. I´m using Xerces, latest version, downloaded a week ago. When i do doc = p

Re: Is the Xerces Document implementation java-serializable?

You *can* Java-serialize the DOM representation, but it's generally a bad idea. Java serialization handles this type of tree structure poorly, and for most documents you'll end up taking much longer to Java-serialize/unserialize than it would take to text-serialize/unserialize. The Java-seriali

Re: Exception

> Ryan D. Cuprak wrote... > > Does anyone know what this error message means or what I maybe doing wrong? This got fixed in 2.0.1. Cheers, Rahul. > Thanks, > Ryan > > java.lang.ArrayIndexOutOfBoundsException > at > org.apache.xerces.util.NamespaceSupport.popContext(NamespaceSupport.jav

Exception

From: Ryan D. Cuprak Does anyone know what this error message means or what I maybe doing wrong? Thanks, Ryan java.lang.ArrayIndexOutOfBoundsException at org.apache.xerces.util.NamespaceSupport.popContext(NamespaceSupport.java:218) at org.apache.xml.serialize.XMLSerializer.endElemen

ASBuilder sample appears not to work with Xerces-J-2.0.1

Hi, With Xerces-J-2.0.1, the ASBuilder sample does not appear to work as expected. I wondered if anyone else has experienced similar problems. First I export my CLASSPATH to include xerces-J-2.0.0, xml-apis and dom.ASBuilder. If I run: java dom.ASBuilder -f -a Response.xsd -i sampleResponse.xml

Is the Xerces Document implementation java-serializable?

Hi If I have an instantiated DOM, can I Java-serialize it (ie, not XML serialization) without restriction? At first glance, it looks like Xerces 2.0 DOM is serializable - is intended to be so through and through? Or is it "java-serialize at your own risk"? Sorry if I missed this in the documentatio

RE: Xerces does not like Rational Quantify (or vice versa)

HI! It turns out that this is a problem between Quantify and JDK 1.4. Regards, Thomas > -Original Message- > From: Thomas Börkel > Sent: Dienstag, 26. Februar 2002 09:53 > To: Xerces Mailinglist > Subject: Xerces does not like Rational Quantify (or vice versa) > > > HI! > > If I try

RE: suppress encoding="UTF-8" while serializing a DOM

Have you looked at the Xalan serializers as an alternative? Rick Bullotta CTO Lighthammer Software (www.lighthammer.com) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Thursday, March 07, 2002 3:23 PM To: [EMAIL PROTECTED] Subject: suppress encoding="UTF-8" whi

ASBuilder schema example

Hi, I have been playing with the ASBuilder example that shows how to validate a set of input xml documents with a xsd schema definition. Currently what this code does is register an error handler that prints out information about what violating nodes were in the parsed input. The error handler i

Re: suppress encoding="UTF-8" while serializing a DOM

[EMAIL PROTECTED] wrote: > In not, and if there's no other Xerces functionality that solves this, you > might consider subclassing java.io.FilterOutputStream to identify and omit > this bit, and simply chain it with your ByteArrayOutputStream. I wouldn't suggest this solution. You'd end up writing

Re: suppress encoding="UTF-8" while serializing a DOM

There is a setOmitXMLDeclaration() method on OutputFormat, if omitting the entire line is acceptable. In not, and if there's no other Xerces functionality that solves this, you might consider subclassing java.io.FilterOutputStream to identify and omit this bit, and simply chain it with your ByteA