Hello,
I am overriding the default parser configuration for enabling XInclude
processing using:
java -Dorg.apache.xerces.xni.parser.XMLParserConfiguration=
org.apache.xerces.xni.parser.org.apache.xerces.parsers.XIncludeParserConfiguration
application_class
I have set the CLASSPATH for "xerces
I guess I didn't notice that in spite of what he said he had his
reply-to address set to xerces-j-user. :(
Bob
Holliday, Donald B. (LNG-CSP) wrote:
I guess you didn't notice that Andy specifically requested that you reply on
the Xerces-J Dev list (xerces-j-dev). That's where he wants to carry on
I guess you didn't notice that Andy specifically requested that you reply on
the Xerces-J Dev list (xerces-j-dev). That's where he wants to carry on a
discussion of this topic. Not on the user list.
Thanks,
Donald Holliday
-Original Message-
From: Bob Foster [mailto:[EMAIL PROTECTED]
Andy Clark wrote:
There are two camps of thought in JSR-173: one that
wants a single interface iterator model and another
that wants discrete event objects to represent the
various parts of the document. The first is designed
with small footprint in mind while the second is more
OO and allows apps
With the recent public review of JSR-173, the Streaming
API for Java, I've been hoping for more of a discussion
among Apache users and developers regarding this API
and pull parsing in general. But there seems to have
been an amazing amount of apathy in this regard. So I
would like to kickstart the
