So you would be one of the users who will be simply using some kind of /dev/null
logger (like org.apache.avalon.framework.logger.NullLogger). What we're
discussing here will enable you to just do that: Switch of logging
messages if you don't want them.

> (I am a user of FOP, not an active developer of FOP, but I do develop 
> apps that use FOP.)
> I've been watching the discussion of logging within FOP rage for at 
> least 6 months now.  It seems pointless to me.
> Logging within FOP is for debugging FOP.  It doesn't need to integrate 
> with anything.  As a user of FOP, I want it to be silent, just like my 
> JDBC driver is silent, just like my AWT layer is silent, just like my 
> messaging driver is silent.  As a developer of FOP, I want logging to 
> debug the FOP code.
> Given the above is true, you could use something as simple as printlns 
> to s global print writer.  In debug mode it would go to the bit bucket. 
>  OK, I've used log4j, so I understand you may want something a little 
> more substantial than that, but why does the user care to integrate FOP 
> debugging into a larger logging structure?

For example to log any warnings should there be any problems later with
the printouts.
> So far, any logging in FOP has been a problem for me.  It fills my logs, 
> and in the old version of FOP I am using, I can't turn it off without a 
> recompile.

So you're still stuck with MessageHandler. You could do something in
your code (just an example):
boolean enableFOPLogging = System.getProperty("fop.log").equals("true");
if (enableFOPLogging) {
} else {

That way you don't have to recompile.

Jeremias Märki


Postfach 3954 - Rhynauerstr. 15 - CH-6002 Luzern
Tel. +41 41 317 2020 - Fax +41 41 317 2029

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]

Reply via email to