The call to run() is not necessary. The transformation is started when
the SAX startDocument() is called by the XSLT Transformer.
On 22.11.2002 13:33:23 Matthias Brunner wrote:
Hello,
I am trying to use FOP by firing SAX events:
fopDriver.setOutputStream(System.out);
Mmm, probably, I think I remember some saying that Crimson doesn't work
correctly. Namespace issues probably. Not sure.
On 22.11.2002 14:19:50 Matthias Brunner wrote:
On Friday 22 November 2002 13:39, Jeremias Maerki wrote:
The call to run() is not necessary. The transformation is started
I believe this problem is due to the options not being set on the XML
renderer or possible a particular option.
It then gets an npe.
The fix of course would be to set the options on the renderer, you can
create the XMLRenderer yourself and set the options on it, then set the
renderer on the
On Friday 22 November 2002 14:26, Jeremias Maerki wrote:
Mmm, probably, I think I remember some saying that Crimson doesn't
work correctly. Namespace issues probably. Not sure.
I tried it on the command line, with classpath und java endorsed dirs
set. Does not help.
BTW: Sorry for mailing 3
Keiron,
On Friday 22 November 2002 14:31, Keiron Liddle wrote:
The fix of course would be to set the options on the renderer, you
can create the XMLRenderer yourself and set the options on it,
then set the renderer on the driver.
thanks for this reply. I found the error. Will post a bug
