Re: XML validation using xml schema string

2003-01-24 Thread Jeff Greif
Try setting the schemalocation of your schema (noNamespaceLocation) to match the fakeLocationURI used for the entity resolver: parser.setProperty("http://apache.org/xml/properties/schema/external-noNames paceSchemaLocation","http://www.contextmedia.com";); parser.setEntityResolver(new SchemaE

Re: XML validation using xml schema string

2003-01-24 Thread Praveen Peddi
Hi Jeff, I did exactly what you told and it doesn't seem to work. Please look at the following code and see if I am doing anything wrong. The error I get is: **Parsing Error**  Line:    1  URI: null  Message: cvc-elt.1: Cannot find the declaration of element 'content'.SAXException Excep

RE: passing null to createCDATASection

2003-01-24 Thread Tim Cronin
thanks for the reply. the problem is is that when I try to Serialize it I get a Null pointer exception. I'm straddling Xerces and Xalan on this, I create the DOM using Xerces which lets me create the cdata with null. But then when I transform it with Xalan I get the Exception. So is this a Bug wi

CR/LF handling

2003-01-24 Thread Scott Moore
I have a text string with carriage returns #xA embedded in it.  When I create a Text node in the latest Xerces DOM with this string, all my carriage returns get converted to a space.  I really need to preserve these carriage returns.  How can I do this?    Thanks, Scott

RE: passing null to createCDATASection

2003-01-24 Thread Christopher Ebert
Hi, Just from thinking about the DOM it seems like it ought to be. You can have an empty CDATA section -- that's what you'd get for passing NULL. Cheers, Chris -Original Message- From: Tim Cronin [mailto:[EMAIL PROTECTED] Sent: Thursday, Janua

Re: Curious benchmarking results

2003-01-24 Thread Andy Clark
Rob Outar wrote: I recently used JProbe to do some benchmarking using Xerces 2, the results I got were sort of confusing. Running a program from within JProbe is a good way to find memory leaks and extraneous object use but is not a good way to measure performance. I think it can show very differe

RE: Curious benchmarking results

2003-01-24 Thread Eric_Schwarzenbach
You might look at a few of the benchmark results people have published, such as: http://sosnoski.com/opensrc/xmlbench/index.html http://piccolo.sourceforge.net/bench.html Also remember that for small to medium documents, the "defer-node-expansion" feature slows Xerces performance significantly-

RE: Curious benchmarking results

2003-01-24 Thread Dr. Robert Spiske
At 09:19 24.01.2003 -0500, you wrote: no comments anyone? I would like to know if my results make sense... Ok, i'll try one. We expect that the validation takes time, so using validation should take longer, as we see. Since you need to read the DTD/XSD to resolve the entities, the memory for the

RE: Curious benchmarking results

2003-01-24 Thread Rob Outar
no comments anyone?  I would like to know if my results make sense...   Thanks,   Rob -Original Message-From: Rob Outar [mailto:[EMAIL PROTECTED]Sent: Thursday, January 23, 2003 10:20 AMTo: [EMAIL PROTECTED]Subject: Curious benchmarking results I recently used JProbe to do so

Re: How to suppress standard out error in Xalan

2003-01-24 Thread Joseph Kesselman
Xalan questions should be routed to the Xalan mailing list, [EMAIL PROTECTED] (As far as I know, most or all Xalan errors should already be going to System.err rather than System.out, so when you post there you might want to say which error is causing trouble.)

How to suppress standard out error in Xalan

2003-01-24 Thread Kumaravel
Hi, I am using Xalan 1.4 C++ and Java. Whenever any error occurs in the transformation, Xalan prints the error on console (std out). I donot want it on console. How to suppress it? Cheers Kumaravel - To unsubscribe, e-mail: [E

RE: problem with null namespace for local attributes in importNode (DOM level 2)

2003-01-24 Thread Aleksandar Milanovic
Hi, Eventually I found an error in the method AttrNSImpl.setName(String namespaceURI, String qname) However, I am not sure if this has been fixed since 2.2.1. The error is that the namespace string was interned, but then the original namespace string used instead of the interned ones. This led t