Thanks for trying this out. I went back to track the problem in detail
and found it was occurring not with the original file, but with a copy
that had gone through a text->DOM->text cycle. The problem is actually
on the output side, using XMLSerializer. This keeps the entity reference
but loses
For simplicity, I put the NekoHTML package I appended to my
original posting on my Apache web site. Check the following
URL for the package:
http://www.apache.org/~andyc/
Has anyone looked at this code and have any comments,
suggestions, etc?
--
Andy Clark * [EMAIL PROTECTED]
--
I had downloaded JAXP Winter Pack on Debian Linux.
I have JDK1.2.2
I use an XML file with very large CData sections( that keep SQL text ).
DocumentBuilderFactory factory =
DocumentBuilderFactory.newInstance();
...
File f = new File("some_file.xml");
As recommended, I enabled the full DOM expansion i.e. set the
defer-node-expansion property to false and executed the same code.
While processing time seemed constant, there was a huge memory leak with
the JVM dying out after reaching 1.5 GB. I have checked to see that
there are no leaks in my tes
Hello,
Is it possible to cache schema grammars using the SAXParser(Xerces
2.0.0)? Any examples/pointers would be much appreciated.
I see that the SAXParser can be constructed with an XMLGrammarPool, but
I am not sure how to create one of them and populate it schema grammars.
Thanks in advance
-Um
Hello,
As Sandy indicates, the XML Schema REC specifies that assessment outcome,
validation errors, etc., are to be recorded in the post-schema-validation
infoset.It is true that if a processor attempts to assess a document
for which there is no schema specified, then generally speaking, it is
already reported
-Original Message-
From: Pavani Mukthipudi [mailto:[EMAIL PROTECTED]
Sent: vrijdag 8 februari 2002 12:53
To: [EMAIL PROTECTED]
Subject: RE: bug xerces 2.0 parsing xml with domparser
Seems to be a bug. Please report it in bugzilla. I'll look into it.
>
> no, we have ma
Seems to be a bug. Please report it in bugzilla. I'll look into it.
>
> no, we have made a gui and we saw that it is with the DOM and not with
> the serialization
> moreover, we use this file for our own 'databinding' where we convert
> xml to dom and dom
> to java objects, so also in this case
xerces parses some files incorrectly, for some files it appends
nodevalues into 1 node
you can easily reproduce it by parsing the sample file and dumping the
dom again to xml
in the dumped xml look for "ie::/DEMET.DEMTRO30/DESADV/44005"
you will see that a little further there are about 20 nodev
E-mail: [EMAIL PROTECTED]
--
||
| Jose Guillén | mailto:[EMAIL PROTECTED] |
| Octalis S.A. | Tf: + 32 (0)10 45
Gude Reshma wrote:
> how can the user the Xerces DOM Parser to parse an HTML document? an
> HTML document is not well formed therfore i'm unable to parse it using
> the Xerces parser. I tried to well form the document using HTML Tidy
> tool given by W3C but this was not helpful. Any suggestions as
Dennis Sosnoski wrote:
> Here's the code (with classpath including xmlParserAPIs.jar and
> xercesImpl.jar):
I'm using your code and I'm still not seeing any problems with
the Xerces 2.0.0 release. Is there any other information you
could provide about your environment?
--
Andy Clark * [EMAIL PRO
hi,
how can the user the Xerces DOM Parser to parse an HTML document? an HTML document is not well formed therfore i'm unable to parse it using the Xerces parser. I tried to well form the document using HTML Tidy tool given by W3C but this was not helpful. Any suggestions as to how i should parse a
[EMAIL PROTECTED] wrote:
>
> > then the parser should report "Validation OK" or it should be silent or
> it should report error?
>
> There are two ways of interpreting the word "report":
>
> 1. The way described by the schema spec: PSVI. When a grammar is not
> available for validating the docum
_
Do You Yahoo!?
Get your free @yahoo.com address at http://mail.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Andy Clark wrote:
Dennis Sosnoski wrote:
I'm getting an exception thrown running Xerces2 (2.0.0) DOMParser:
This is very strange because I tried your document with Xerces
2.0.0 and I don't see these problems. (I'm using the dom.*
samples to test it.)
What is the exact invocation code you are using?
16 matches
Mail list logo