DO NOT REPLY [Bug 32193] New: - NullPointerException when using non-Apache XML parser (Xerces) and/or JXTransformer

/show_bug.cgi?id=32193 NullPointerException when using non-Apache XML parser (Xerces) and/or JXTransformer Summary: NullPointerException when using non-Apache XML parser (Xerces) and/or JXTransformer Product: Fop Version: 0.20.5 Platform

DO NOT REPLY [Bug 32193] - NullPointerException when using non-Apache XML parser (Xerces) and/or JXTransformer

/show_bug.cgi?id=32193 NullPointerException when using non-Apache XML parser (Xerces) and/or JXTransformer [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW

Re: [VOTE] Centralize parser creation/Simpler internal rendering calls

is actually of legitimate use. Actually I don't mind the design of InputHandler and its subclasses now that I understand their purpose! We should probably still get rid of one of Trax/XSLTInputHandler, due to their duplicative functionality though. 2) The other vote, that below, of moving the parser

[VOTE] Centralize parser creation/Simpler internal rendering calls

this into the Driver class, and have a single createParser() function in one place. I realize that Driver may be going out the window soon, so whatever replaces it will have full control over parser-creating duties. With this change, all internal calls of the Driver.render() functions will no longer need

Re: [VOTE] Centralize parser creation/Simpler internal rendering calls

Yes, I said InputHandler is where the parser is created--I just want that moved over to Driver (because driver is creating them to, with its own local instance, for external servlet usage). This will help Victor's API simplification, also might help us deprecate InputHandler a bit. When TRAX

Re: [VOTE] Centralize parser creation/Simpler internal rendering calls

package reference the configuration package. And it's almost the same code and with the same semantics everywhere so this would actually reduce code. On 21.07.2003 18:20:30 Glen Mazza wrote: Yes, I said InputHandler is where the parser is created--I just want that moved over to Driver

Re: PPD parser (was: generate pdf files and print them to a specific paper bin)

Uh, if you manage to come up with a reasonable start for a PPD parser that would be cool. On 16.01.2003 18:49:33 Arnd Beißner wrote: For a customer who urgently needed the same kind of thing, we switched to PostScript output with FOP and extended (well, so far it's rather a hack) FOP's PS

DO NOT REPLY [Bug 10287] - fop 0.20.4RC is unable to run with Aelfred xml parser

/show_bug.cgi?id=10287 fop 0.20.4RC is unable to run with Aelfred xml parser [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED

Trouble with XML parser versions...

) at org.apache.catalina.connector.http.HttpProcessor.process(HttpProcessor.java:1011) at org.apache.catalina.connector.http.HttpProcessor.run(HttpProcessor.java:1106) at java.lang.Thread.run(Thread.java:536) I've cleaned my classpath of any XML parser jars to insure I'm using the reference

DO NOT REPLY [Bug 10287] New: - fop 0.20.4RC is unable to run with Aelfred xml parser

/show_bug.cgi?id=10287 fop 0.20.4RC is unable to run with Aelfred xml parser Summary: fop 0.20.4RC is unable to run with Aelfred xml parser Product: Fop Version: 0.20.4 Platform: PC OS/Version: Other Status: NEW Severity: Normal

parser

Hi all, i have a problem with the fop. i can generate a pdf from a fo file, but i can´t generatethe fo file. Some person´s told me that the problem would reside in the server, that probably uses another parser, but i think that is not the problem. My server is Apache JServ 1.0 JAR's xalan

AW: parser

op. i can generate a pdf from a fo file, but i can´t generatethe fo file. Some person´s told me that the problem would reside in the server, that probably uses another parser, but i think that is not the problem. My server is Apache JServ 1.0 JAR's xalan-2.0.0.jar, xerces-1.2.3.jar

Re: uri parser?

Keiron, Thanks. I was looking at the handling of 'url(...)' in the property expression parser, and I thought that the general solution would be a uri parser. Peter Keiron Liddle wrote: On 2001.11.20 16:23 Peter B. West wrote: Does anyone know of a general URI parser tucked away

uri parser?

Does anyone know of a general URI parser tucked away in the code somewhere, or failing that, available elsewhere? Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest Lord, to whom shall we go

Re: uri parser?

Peter B. West wrote: Does anyone know of a general URI parser tucked away in the code somewhere, or failing that, available elsewhere? How about java.net.URL? Ulrich -- Ulrich Mayring DENIC eG, Systementwicklung

RE: uri parser?

Subject: uri parser? Does anyone know of a general URI parser tucked away in the code somewhere, or failing that, available elsewhere? Peter -- Peter B. West [EMAIL PROTECTED] http://powerup.com.au/~pbwest Lord, to whom shall we go

Re: uri parser?

for a URI-SPECIFICATION in PropertyParser, and wondered whether it was easy to find a parser. Peter Ulrich Mayring wrote: Peter B. West wrote: Does anyone know of a general URI parser tucked away in the code somewhere, or failing that, available elsewhere? How about java.net.URL? Ulrich

Antwort: XML parser question

Willie Wu wrote: Is it possible to configure FOP to use a XML parser other than Xerces? In my existing app, I'm already using Crimson, which I want to reuse for FOP. Yes, it is possible. It's a little bit arcane, though: you'll have to set the javax.xml.parsers.SAXParserFactory service

XML parser question

Is it possible to configure FOP to use a XML parser other than Xerces? In my existing app, I'm already using Crimson, which I want to reuse for FOP. Thanks. _ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

Namespace not supported by Parser ??

Hi all, I set the feature and I am getting the following error. It seems to throw error at org.xml.sax.XMLReader parser = inputHandler.getParser(); So I am not sure If setting the feature afterwards will be of any use.What must I add in ?Is the setting