Thank you. I don't want to set the filename or maintain the appender from my program. This is up to the operators running the application. And I don't want to add limitations beyond those given by logback itself. I thought logback would know the file it uses - why not supply the name? I could also (and I do it already) set the logfile by the operationg system and provide the name as an argument. In this case the I must request that only the console-appender can be used. But I don't like this approach. Ulrich Am 31.07.2013 12:21, schrieb David Roussel:
I've made my app know the logger file name so that I can put a link to it in an email.
Buy the way I did it was to make the app choose the filename and set a system property. Then in logback.xml refer to the system property.
If that approach does not work, because you are using a dynamic log file name, then I suggest you try subclassing the rolling appender and getting the new filename each time one is generated, and then putting that value into a static singleton that is visible to your app.
David
On 31 Jul 2013, at 11:12, Ulrich <Forums@gombers.de> wrote:
Within my application I would like to know the filename used by it's logger. I've asked this question before but didn't get an answer. So I will give it another try. I've browsed through the Javadoc of the classes and interfaces where I thought by their name they should be able to provide this piece of information (LoggerContext and Appender to name two of them), but wasn't lucky.
Can anyone help here? Ulrich
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user
_______________________________________________ Logback-user mailing list Logback-user@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-user