On Fri, Jun 24, 2005 at 08:13:47AM -0600, Will Peterson wrote:
Simon,
Not sure if I'm looking in the right place ... but checked under the CVS and
SVN versions of the FOP project, but can't find any folder named
private-resources.
Funny, I have always believed it was part of the FOP
repository. Apparently it is not. Here they are:
commons-logging.properties:
# common-logging.properties
# configuration file for org.apache.commons.logging.Log
# log implementation to use
org.apache.commons.logging.Log=org.apache.commons.logging.impl.SimpleLog
simplelog.properties:
# simplelog.properties
# configuration file for org.apache.commons.logging.impl.SimpleLog
# logging level for all loggers, default info
# org.apache.commons.logging.simplelog.defaultlog=info
# logging level for named loggers
# org.apache.commons.logging.simplelog.log.x=info
# org.apache.commons.logging.simplelog.log.org.apache.fop.pdf=trace
# show logger name, default false
# org.apache.commons.logging.simplelog.showlogname=false
# show short logger name, default true
# org.apache.commons.logging.simplelog.showShortLogname=false
# show date and time, default false
# org.apache.commons.logging.simplelog.showdatetime=false
Regards, Simon
Thanks for your help,
- Will
On 6/23/2005 at 2:44 pm, [EMAIL PROTECTED] wrote:
Will,
I am answering you on fop-user.
See xml-fop/src/private-resources for an example of how to configure
logging with SimpleLog (org.apache.commons.logging.impl.SimpleLog). If
you want to selectively change the log level for some loggers, you
will have to dig in the code for the logger names. Often they are the
package or class name.
Regards, Simon
On Thu, Jun 23, 2005 at 08:16:34PM +0200, Jeremias Maerki wrote:
Will,
we haven't had any chance, yet, to write more than design documentation
on 1.0dev. 1.0dev uses Jakarta Commons Logging [1] as logging framework.
This means that on a standard JDK 1.4 (or higher) system JCL uses JDK
logging as its backend by default. For this case you'd have to look up
the documentation for JDK logging [2]. It's pretty easy to supply your
own logger of choice. The JCL documentation will tell you how to do that.
In contrast to Avalon loggon JCL logging uses more or less the same
approach as Log4J which normally fetches the logger per class into a
static variable. That's why you can't set a logger directly on the
Driver (or rather Fop now) instance.
I believe that until the final 1.0 release it is possible that in the
area of logging of few things may still change. Probably not the use of
JCL but maybe a specialized facility to observe the formatting process
programmatically. There's nothing written in stone about that, yet. And
until then, consider 1.0dev a moving target. Suggestions and help are
welcome.
HTH
[1] http://jakarta.apache.org/commons/logging/ (version 1.0.3)
[2] http://java.sun.com/j2se/1.4.2/docs/guide/util/logging/index.html
On 23.06.2005 18:18:19 Will Peterson wrote:
Is there any sample documentation on how to do logging with Fop 1.0dev.
The previous Fop had examples right in the distribution, but I can't
find anything there, or on the web for sample code of how to do logging.
(All the code example I see are based on having a handle on the driver
(for example):
//Setup logger
Logger logger = new ConsoleLogger(ConsoleLogger.LEVEL_INFO);
driver.setLogger(logger);
MessageHandler.setScreenLogger(logger);
Thanks for any help,
- Will
Jeremias Maerki
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Simon Pepping
home page: http://www.leverkruid.nl
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
