[
https://issues.apache.org/jira/browse/PDFBOX-472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12709566#action_12709566
]
Jeremias Maerki commented on PDFBOX-472:
----------------------------------------
Well, it's relatively easy to re-route JDK logging to any other logging
framework. But I guess abstractions such as JCL or SLF4J make that a bit
easier. At any rate, logging to a file by default is probably not the best idea
as Sean hints at. For a command-line application, not a problem, but when
PDFBox is used embedded it's better to leave logging configuration to the user
of the library. In Apache FOP we're using JCL and are mostly happy with the
choice. The only problem (solved in the meantime) was to isolate event message
per document being processed in a multi-threaded environment. Similar problem
in PDFBox maybe (depending on the requirements). See
http://xmlgraphics.apache.org/fop/trunk/events.html for what I came up with.
Additional opinions?
> use commons logging
> -------------------
>
> Key: PDFBOX-472
> URL: https://issues.apache.org/jira/browse/PDFBOX-472
> Project: PDFBox
> Issue Type: Improvement
> Affects Versions: 0.8.0-incubator
> Reporter: Sean Bridges
> Fix For: 0.8.0-incubator
>
> Attachments: logpatch
>
>
> LoggingObject logs all pdfbox output to a file PDFBox.log using
> java.util.logging. The app may not have permission to create this file, the
> user probably won't be looking at it for errors, and for long running server
> tasks, this file may grow very large.
> It would be much nicer to simply use apache commons logging (or even SLF4J)
> and allow the application to setup logging as they see fit.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
