Providing schema at a node

HI! I am trying to provide a schema for a node, not for the whole document. Xerces 2.4.0 does not report a schema error in this case. Example: book.xsd: http://www.w3.org/2001/XMLSchema";>

RE: Namespace problem with Xerces >2.0.1

HI! Thanks for the explanation. I think I understand now both cases better. The XPathAPI is part of Xalan, but it does not do anything wrong here, right? We still need to add your code suggestion from yesterday, because the Xalan Transformer (we use that for saving to file) apparently also does

RE: Namespace problem with Xerces >2.0.1

HI! Thanks for the fast response. It looks similar to the problem yesterday, but we fixed that one by changing our code like you suggested, so that we "did it right". We didn't want the Serializer to *fix* something that we "did wrong", so we did not turn the namespace fixup on there. So, yo

Namespace problem with Xerces >2.0.1

HI! We ran into another namespace problem after switching to Xerces 2.4.0. We are searching a node with Xalan 2.4.1 and then output the node as string. Xerces 2.4.0 Serializer does not provide the full namespace information of that node, where 2.0.1 does, so that this node cannot stand alone an

RE: createElementNS() does not work as expected in new versions of Xerces (> 2.0.1)

HI! Thanks for the clarification. Regards, Thomas > -Original Message- > From: Elena Litani [mailto:[EMAIL PROTECTED] > Sent: Montag, 26. Mai 2003 16:35 > To: [EMAIL PROTECTED] > Subject: Re: createElementNS() does not work as expected in > new versions of Xerces (> 2.0.1) > > > Hi T

createElementNS() does not work as expected in new versions of Xerces (> 2.0.1)

HI! We used createElementNS() in 2.0.1 successfully. Since we switched to newer versions (now 2.4.0), it stopped working as expected. We have reviewed our code and changed it as suggested in http://nagoya.apache.org/bugzilla/show_bug.cgi?id=7687 with no positive effect. Using 2.0.1, the test c

RE: Error parsing files, when filename contains german umlauts

Canada > (1-905) 413-3255 > [EMAIL PROTECTED] > > > > >

RE: Error parsing files, when filename contains german umlauts

Correction: 2.2.0 still has problems with spaces in the path. :-( > -Original Message- > From: Thomas Börkel > Sent: Montag, 14. Oktober 2002 08:59 > To: [EMAIL PROTECTED] > Subject: RE: Error parsing files, when filename contains > german umlauts > > >

RE: Error parsing files, when filename contains german umlauts

2.2.0 seems to work OK with both spaces and umlauts. > -Original Message- > From: Thomas Börkel > Sent: Freitag, 11. Oktober 2002 09:59 > To: [EMAIL PROTECTED] > Subject: RE: Error parsing files, when filename contains > german umlauts > > > HI! >

RE: Error parsing files, when filename contains german umlauts

HI! We had the same problem and switched back to 2.0.1 because of this. Haven't tested the new 2.2.0 release, yet. Regards, Thomas > -Original Message- > From: Amthauer, Heiner [mailto:[EMAIL PROTECTED] > Sent: Freitag, 11. Oktober 2002 09:28 > To: 'Xerces' > Subject: Error parsing fil

RE: Getting parsing errors when specified schema file which has embedded space 'in its name' or 'in its path' ...

HI! I think I have the same or a similar problem here. 2.0.1 works, but 2.0.2 and 2.1.0 not. We don't use a path in the schema reference (only the file name), but we get problems, if the path to the XML has spaces. I filed a bug report: http://nagoya.apache.org/bugzilla/show_bug.cgi?id=12257

Cannot report bugs for 2.1.0

HI! I cannot choose version 2.1.0 on http://nagoya.apache.org/bugzilla/enter_bug.cgi?product=Xerces2-J. Regards, Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Xerces-J 2.1.0 and bug #10485

HI! Version 2.0.2 introduced bug #10485 (and also bug #10468, which is possibly related), and this one is still present in 2.1.0. This locks us into 2.0.1. Could someone please look at that? Thanks! Regards, Thomas - To unsu

RE: Xerces - trying to find the DTD throws a MalformedURLException

HI! Xerces 2.0.2 has problems with spaces in file names, where 2.0.1 did not. For example, you cannot load an XML if your CURRENT path has a space. I have filed a bug report for this and you should file one for your problem, too. Regards, Thomas > -Original Message- > From: Panos Konst

RE: XMLSerializer: Escaping of single quotes

6:10 > To: [EMAIL PROTECTED] > Subject: Re: XMLSerializer: Escaping of single quotes > > > Hi Thomas, > > Thomas Börkel wrote: > > The XMLSerializer escapes single quotes ('). Why? If I want > to transfrom the string back into a Document object, > un-escaped si

XMLSerializer: Escaping of single quotes

HI! The XMLSerializer escapes single quotes ('). Why? If I want to transfrom the string back into a Document object, un-escaped single quotes work pretty well. Escaping <, > and & is OK, but why '? Thanks! Regards, Thomas -

OutputFormat.setNonEscapingElements() for ALL nodes?

HI! I can specify with setNonEscapingElements() for which nodes the text childs should be output non-escaped. How can I set this globally, if I don't know all nodes? I have tried: outputFormat.setNonEscapingElements(new String[]{"*"}); outputFormat.setNonEscapingElements(new String[]{""}); out

MalformedURLException instead of FileNotFoundException since 2.0.2

HI! If I try to parse (with DocumentBuilder) a non-existent XML document from hard disk (Windows 2000, filename="C:\something.xml"), I do not get a FileNotFoundException but a MalformedURLException ("unknown protocol: c") since 2.0.2. This was OK in 2.0.1. Regards, Thomas ---

Bugzilla: Cannot report bugs for 2.0.2

HI! In Bugzilla, I can only report bugs for Xerces up to 2.0.1. Regards, Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

NPEs in Xerces code

HI! Xerces throws pretty often NullPointerExceptions and catches them itself. But this is annoying if I am searching for my own NPEs and set a breakpoint on occurring NPEs. Is there a chance that this will be changed in Xerces? Regards, Thomas -

RE: How to find out the version of Xerces programmatically?

Answering my own question: org.apache.xerces.impl.Version > -Original Message- > From: Thomas Börkel > Sent: Dienstag, 2. April 2002 10:05 > To: Xerces Mailinglist > Subject: How to find out the version of Xerces programmatically? > > > HI! > > How

How to find out the version of Xerces programmatically?

HI! How can I find out the version of Xerces that my program uses? Is there some kind of main class with a version string? Thanks! Regards, Thomas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [

Wrong behavior of XMLSerializer or documentation bug

HI! Giving an XMLSerializer an OutputFormat with setPreserveSpace(true) should preserve spaces. Actually, this preserves LFs. Spaces are preserved always. Example: xml = "\n \n \n \n\n"; sw = new StringWriter(); outputFormat = new OutputFormat(); outputFormat.setOmitXMLDecl

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) > >

RE: Bad bug in handling of extra spaces

ling of extra spaces > > > Probably because Xerces thinks it's not ignorable at all (I > think it can > only be "ignorable" in the presence of a DTD). > > You'd better update your code to handle whitespace text nodes... > > > -Original M

RE: Bad bug in handling of extra spaces

itespace. > > > -Original Message- > > From: Thomas Börkel [mailto:[EMAIL PROTECTED] > > Sent: Monday, March 04, 2002 1:56 PM > > To: [EMAIL PROTECTED] > > Subject: RE: Bad bug in handling of extra spaces > > > > > > HI! > > >

RE: Bad bug in handling of extra spaces

ting spaces" are whitespace and thus are reported as > text nodes. > > > -Original Message- > > From: Thomas Börkel [mailto:[EMAIL PROTECTED] > > Sent: Monday, March 04, 2002 1:38 PM > > To: Xerces Mailinglist > > Subject: Bad bug in handling o

Bad bug in handling of extra spaces

HI! Xerces (tested with current build) handles formatting spaces as elements of type text. Example 1: xml = "\r\n \r\n \r\n"; Example 2: xml = ""; The 2 examples produce 2 different DOMs! The first one produces an incorrect DOM. You can test it with this code: Document doc;

Recommended way to implement toString() for a node?

HI! What's the recommended way to implement a toString() method for an xml node? Currently, I do: StreamResult streamResult; Transformer transformer; String result; streamResult = new StreamResult(new StringWriter()); transformer = TransformerFactory.newInstance().newTransformer();

Schema validation dynamic not working anymore in current build?

HI! If I set the attribute "http://apache.org/xml/features/validation/dynamic"; to true with Xerces 2.0.0, then I can load an XSLT document without warning (it cannot find the XSLT schema). Using the current build, this generates a warning. Which version of Xerces is doing it right? Is there su

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

Xerces does not like Rational Quantify (or vice versa) > > > > > > -Original Message- > > From: Thomas Börkel [mailto:[EMAIL PROTECTED] > > In those 2 stacktraces, it's JAXP and SAX. > > Is crimson sneaking into the mix? Are there any other DOM

RE: Bad bug in Xerces?

HI! Thanks for both quick answers. I confirm that this bug is fixed in the current build. But, the current build now generates a warning for missing schemas, even with schema validation dynamic. Is this intended? Regards, Thomas > -Original Message- > From: Thomas Börkel

RE: Bad bug in Xerces?

nside. Do I have to compile and build this jar-file myself from the current sources? Couldn't this be integrated into the nightly build process (just wondering)? > -Original Message- > From: Thomas Börkel > Sent: Dienstag, 26. Februar 2002 12:54 > To: Xerces Mailinglist

Bad bug in Xerces?

HI! Consider the following XML, which is being built with dbf = DocumentBuilderFactory.newInstance(); db = dbf.newDocumentBuilder(); doc = db.parse(new InputSource(new StringReader(text))): If you write out the document after this with streamResult = new StreamResult(new StringWriter()); tra

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

HI! > > That's a misunderstandung. Quantify does not use Java code, it > > just profiles it. The stacktraces are from our product's code > > and Xerces throws those Errors only if we start our code with > > the Quantify starter. > > Gotcha. But I'd still ask if you are using any direct > APIs

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

k [mailto:[EMAIL PROTECTED] > Sent: Dienstag, 26. Februar 2002 10:19 > To: [EMAIL PROTECTED] > Subject: Re: Xerces does not like Rational Quantify (or vice versa) > > > Thomas Börkel wrote: > > If I try to use Rational Quantify 2002 with JDK 1.4 to profile > > my p

Xerces does not like Rational Quantify (or vice versa)

HI! If I try to use Rational Quantify 2002 with JDK 1.4 to profile my program, I get a NoClassDefNotFoundError in the Xerces code!? Anyone seen this or have an explanation for this? Here are 2 example stacktraces: java.lang.NoClassDefFoundError: Rational/QProfJ at org.xml.sax.InputSou