I've commented out the offending code. I don't really know what to do
with it. It would probably be cleanest if the cli package wrote to the
console using System.out/err only and only sets up the logger for the
rest of FOP. Hmmm.

On 19.09.2005 15:05:26 Manuel Mall wrote:
> Luca,
> 
> not sure if this is it but in CommandLineOptions we have:
> 
> if (System.getProperty("org.apache.commons.logging.Log") == null) {
>      logFactory.setAttribute("org.apache.commons.logging.Log",
>                                  CommandLineLogger.class.getName());
>        setLogLevel("info");
> }
> log = LogFactory.getLog("FOP");
> 
> i.e. the log instance is created after the call to setLogLevel(...). But 
> setLogLevel starts with:
> ...
> if (log instanceof CommandLineLogger) {
> 
> so you are hitting a likely NPE here.
> 
> Manuel
> On Mon, 19 Sep 2005 08:57 pm, Luca Furini wrote:
> > Hi all.
> >
> > I'm noticing a strange problem: fop builds correctly, but then it
> > seems it is not working at all.
> >
> > I'm using it from the command line under win xp, and even if I don't
> > get any run time exception no output file is created. Launching fop
> > with no parameters, or with wrong parameters (missing files ...) does
> > not create any error: simply, nothing happens.
> >
> > I have compiled fop on two different computers, so I don't think this
> > is a local configuration problem.
> >
> > Hasn't anyone else noticed this?
> >
> > Regards
> >      Luca



Jeremias Maerki

Reply via email to