Elliotte Rusty Harold wrote:
At 9:07 PM -0800 3/4/04, Clay Leeds wrote:
- if XMLReaderFactory works under JDK 1.3 and/or 1.2, what kinds of
benefits might fop-0.20.5 see from a switch to XMLReaderFactory?
Cleaner simpler code that's less likely to get hosed by different
implementations
At 8:53 PM +0100 3/5/04, Simon Pepping wrote:
It took me a little while, but I now remember again why I did not want
to use the XMLReaderFactory. I do not understand how I can guarantee
that I get an XMLReader that is capable of validation. In
SAXParserFactory I can configure the factory to look
By the way, if you're curious you can look at the code for
SAXParserFactory (and its default concrete subclass in Java 1.4) in
the Apache Crimson CVS (which is ungodly slow today, not sure why).
It's easy to see that it never returns any parser other than Crimson,
regardless of what features
Glen Mazza wrote:
--- Peter B. West [EMAIL PROTECTED] wrote:
...
That is, I would turn allow the namespace-prefixes
feature to remain in
its default 'false' state, but make sure the parser
is namespace aware.
I don't know that there is any reason for us to
collect prefixes,
This is
At 12:56 PM +1000 3/4/04, Peter B. West wrote:
Fops,
In HEAD, ///apps/FOFileHAndler.java contains the following:
protected static XMLReader createParser() throws FOPException {
try {
SAXParserFactory factory = SAXParserFactory.newInstance();
--- Elliotte Rusty Harold [EMAIL PROTECTED]
wrote:
What I ask on reading this code is why you're using
SAXParserFactory
at all? SAXParserFactory is a Sun class they
invented to fill a hole
in SAX 1.0. It's unnecessary in SAX 2.0. SAX2 apps
should use
XMLReaderFactory instead, which has
At 2:36 PM -0800 3/4/04, Glen Mazza wrote:
--- Elliotte Rusty Harold [EMAIL PROTECTED]
wrote:
What I ask on reading this code is why you're using
SAXParserFactory
at all? SAXParserFactory is a Sun class they
invented to fill a hole
in SAX 1.0. It's unnecessary in SAX 2.0. SAX2 apps
should
Elliotte Rusty Harold wrote:
At 12:56 PM +1000 3/4/04, Peter B. West wrote:
...
SAXParserFactory factory = SAXParserFactory.newInstance();
factory.setNamespaceAware(true);
return factory.newSAXParser().getXMLReader();
...
What I ask on reading this code is why
At 10:43 AM +1000 3/5/04, Peter B. West wrote:
I think this might be because the HEAD developers were moving to a
JAXP implementation, and SAXParserFactory is still in the 1.4
javax.xml.parsers package, which, AIUI, is what one is supposed to
use for JAXP-compatible applications. I don't know
On Mar 4, 2004, at 6:53 PM, Elliotte Rusty Harold wrote:
At 10:43 AM +1000 3/5/04, Peter B. West wrote:
I think this might be because the HEAD developers were moving to a
JAXP implementation, and SAXParserFactory is still in the 1.4
javax.xml.parsers package, which, AIUI, is what one is
On Mar 4, 2004, at 6:53 PM, Elliotte Rusty Harold wrote:
At 10:43 AM +1000 3/5/04, Peter B. West wrote:
I think this might be because the HEAD developers were moving to a
JAXP implementation, and SAXParserFactory is still in the 1.4
javax.xml.parsers package, which, AIUI, is what one is
--- Peter B. West [EMAIL PROTECTED] wrote:
In HEAD, ///apps/FOFileHAndler.java contains the
following:
factory.setFeature(
http://xml.org/sax/features/namespace-prefixes;,
true);
snip/
That is, I would turn allow the namespace-prefixes
feature to remain in
12 matches
Mail list logo
