RE: : Using saxon-fop - NullPointerException

I've now done the changes that make Saxon work with FOP 0.20.3. I'm afraid
they were non-trivial - once again, FOP has changed the API on me. This time
it's a new requirement to create and supply a "Logger" object, something
that appears to require invoking five other classes in three separate
packages in a different Apache project.

This is the last time - if they do this to me again, Saxon/FOP integration
will be dropped.

Michael Kay
Software AG
home: Michael.H.Kay@xxxxxxxxxxxx
work: Michael.Kay@xxxxxxxxxxxxxx

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> [mailto:owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx]On Behalf Of
> J.Pietschmann
> Sent: 19 April 2002 20:19
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> Subject: Re: : Using saxon-fop - NullPointerException
>
>
> TSchutzerWeissmann@xxxxxxxxxxxxxxxx wrote:
> > Everything went swimmingly (except a minor error message
> because no logger
> > had been set) until the last page of my document.
> >
> >       java.lang.NullPointerException
> > 	at
> > org.apache.fop.apps.StreamRenderer.render(StreamRenderer.java:205)
>
> At this point the StreamRenderer tries to log the
> total page count. I guess there hasn't been a logger
> set for the stream renderer. A quick glance into
> com.icl.saxon.fop.FOPEmitter seems to confirm this,
> an explicite StreamRenderer is createt there (as a
> workaround for a FOP 0.20.1 deficency), and no logger
> is set.
>
> Because you have the source, you can fix that yourself,
> deleting the statement mentioned above should be sufficient.
>
> J.Pietschmann
>
>
>
>
>
>  XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list
>


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list