[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [virgo-dev] Including logback.xml in the bundle
- From: Glyn Normington <gnormington@xxxxxxxxxx>
- Date: Fri, 23 Jul 2010 00:39:22 -0700
- Accept-language: en-US
- Acceptlanguage: en-US
- Delivered-to: email@example.com
- Thread-index: AcsqOir7RwhfXsFVRRGWST5pw00B7g==
- Thread-topic: [virgo-dev] Including logback.xml in the bundle
I should have mentioned that a user can configure Logback for a given bundle by adding a file called logback.xml (or logback-default.xml) to the root of the bundle.
This function should be exercised by MedicLoggingIntegrationTests. The test naming could be better, but test_bundle_1 and test_bundle_2 both use per-bundle configuration.
On 23 Jul 2010, at 07:23, Glyn Normington wrote:
> Hi Dmitry
> There is support for that built into medic, so perhaps you've found a (basic) bug.
> If you want to dig into this, please take a look at the following medic classes.
> Reading the config out of a bundle is handled by BundleResourceConfigurationLocator. The different ConfigurationLocators are combined and called in order by CompositeConfigurationLocator which is created in MedicActivator.
> On 22 Jul 2010, at 15:35, Dmitry Sklyut wrote:
>> Is there support for including logback.xml together with the deployed bundle? All of the things that I tried did not work.
>> During 2gx last year Rob and Ben mentioned that it is possible. I am wondering if I am missing some manifest header or some magic pixie dust to get it to work.
>> Looking at the medic code I did not see any extender like functionality for look for bundle/logback.xml or bundle/META-INF/logback.xml...
>> I have a use case where I would like to re-use logging framework to write out log file into a separate file per instance of Spring Batch job.
> virgo-dev mailing list