Hi:
Any way(s) to prevent/disable buffering in Xerces2?
Similar to Xerces1 "read data from a stream as it arrives" functionality where parser.setReaderFactory(new StreamingCharFactory()); and so on. as described in http://xml.apache.org/xerces-j/faq-write.html#faq-11.
However for Xerces2 I am
Hi,
I have problem with SAX bit of Xerces. I use SAX to get lines of an element
of specified tag and print them out.
I was using older version of Xerces with which it run fine. When I replaced
old xerces.jar with new xercesImpl.jar SAX starts to behave wierd.
CDATA element content which is
At 3:48 PM + 1/16/04, Michal Sankot wrote:
Hi,
I have problem with SAX bit of Xerces. I use SAX to get lines of an element
of specified tag and print them out.
I was using older version of Xerces with which it run fine. When I replaced
old xerces.jar with new xercesImpl.jar SAX starts to
I would like to be able to trap and handle various types of SAXParseException
differently. Primarily, I would like to be able to trap the following:
org.xml.sax.SAXParseException: An invalid XML character (Unicode: XXX) was
found in the element content of the document.
Where XXX is any of
In the upcoming release of Xerces-J
we are going to be including OASIS XML Catalog [1] support which will allow
users to resolve locations for their schemas (using their target namespaces),
DTDs and other external entities using a catalog. The XML Commons
resolver [2] which implements XML
Hello!
I have two questions:
(1) I want to preserve comments in the following lines, but it does not
work: comments are still removed.
memoryxml.reset();
try {
InputSource input = new InputSource(memoryxml);
input.setEncoding(utf-8);
Hello!
I have two questions:
(1) I want to preserve comments in the following lines, but it does not
work: comments are still removed.
memoryxml.reset();
try {
InputSource input = new InputSource(memoryxml);
input.setEncoding(utf-8);
This seems a good thing to do! Some feedback and questions...
- Please don't do anything that will interfere with the operation of
entity reolvers. If an entity resolver returns anything other than null,
don't re-resolve the result with a catalog. IOW, a catalog should be
consulted only if
Hi Bob,
my comments are below...
On Fri, 16 Jan 2004, Bob Foster wrote:
This seems a good thing to do! Some feedback and questions...
- Please don't do anything that will interfere with the operation of
entity reolvers. If an entity resolver returns anything other than null,
don't
