/show_bug.cgi?id=32225
[PATCH] prefixed attibutes for fo: namespace
Summary: [PATCH] prefixed attibutes for fo: namespace
Product: Fop
Version: 0.20.5
Platform: All
OS/Version: All
Status: NEW
Severity: Enhancement
Priority
in the recent past.
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 for a validating
and namespace-aware
for a validating
and namespace-aware parser. In XMLReaderFactory, it may produce an
XMLReader which throws an exception when I want to set the validating
feature on it.
This is a new one for me, and I can see how you might think
SAXParserFactory guarantees validation by looking at the API docs
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
();
factory.setNamespaceAware(true);
factory.setFeature(
http://xml.org/sax/features/namespace-prefixes;, true);
return factory.newSAXParser().getXMLReader();
} catch (SAXNotSupportedException se) {
throw new FOPException(Error: You need a parser which allows
--- 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
(
http://xml.org/sax/features/namespace-prefixes;, true);
return factory.newSAXParser().getXMLReader();
} catch (SAXNotSupportedException se) {
throw new FOPException(Error: You need a parser which
allows the
+ http://xml.org/sax
--- 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
(;
[2001/10/30 11:35:02][1 ][I]: ** Transformer Factory error
[2001/10/30 11:35:02][1 ][I]:
javax.xml.transform.TransformerConfigurationException:
javax.xml.transform.TransformerException: Namespace not supported by
SAXParser
Does anyone know this error?
Gerard
An: '[EMAIL PROTECTED]'
Betreff: NameSpace??
Hello,
ClassLoader loader = this.getClass().getClassLoader();
URL url = loader.getResource(cv.xsl);
System.out.println(url);
TransformerFactory tFactory = TransformerFactory.newInstance();
Transformer transformer = tFactory.newTransformer(new
, your problem may be completely unrelated.
YS
-Original Message-
From: Gerard van Wijk [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 30, 2001 5:41 AM
To: '[EMAIL PROTECTED]'
Subject: NameSpace??
Hello,
ClassLoader loader = this.getClass().getClassLoader();
URL url
Thomas, Mary [EMAIL PROTECTED] wrote on Mon Aug 13, 2001:
I am trying to figure out why exactly there is this namespace issue.
Precisely, what error messages are you getting? It would help
greatly if were to describe the problem rather than saying just this
namespace
issue.
I am wondering
);
driver.render();
javax.xml.parsers.ParserConfigurationException: Namespace not supported by
SAXParser
at com.sun.xml.parser.SAXParserImpl.init(SAXParserImpl.java:60)
at
com.sun.xml.parser.SAXParserFactoryImpl.newSAXParser(SAXParserFactoryImpl.ja
va:57
.
javax.xml.transform.TransformerConfigurationException: Namespace not
supported by SAXParser
import javax.servlet.*;
import javax.servlet.http.*;
import java.io.*;
import java.util.*;
import org.apache.fop.apps.*;
import org.xml.sax.*;
import javax.xml.transform.*;
import javax.xml.transform.Source;
import
Hi Mary:
You are Missing the code that sets the namespace feature.
After making a call to the create Parser, you need to set features. I have
included it below.
Vallikun
try{
XMLReader xmlreader =createParser();
// set the parser
.
javax.xml.transform.TransformerConfigurationException: Namespace not
supported by SAXParser
Try using org.apache.fop.apps.TraxInputHandler. It lets you specify
the files for the input XML and XSLT and gives you back an XMLReader and
InputSource for use with buildFOTree(). That should allow you to skip
the buffering you
I am facing a problem:
When I use fop_15 from the server. It is working all right, but the same code
doesn't work for fop_14.
It gives the error - Unknown namespace prefix fo
Even the sample file which is provided with FOP version_14 also doesn't work.
My xsl file looks like this.
?xml
23 matches
Mail list logo
