[jboss-as7-dev] logger config per deployment / app

[Ales Justin]

Is this on by default?

LoggingConfigurationProcessor

    private VirtualFile findConfigFile(ResourceRoot resourceRoot) throws DeploymentUnitProcessingException {
        VirtualFile result = null;
        try {
            final List<VirtualFile> configFiles = resourceRoot.getRoot().getChildrenRecursively(ConfigFilter.INSTANCE);
            for (final VirtualFile file : configFiles) {

As this looks slow ...

On May 25, 2012, at 12:13 AM, James Perkins wrote:

> Only if you add a logging.properties file to your deployment. Once you 
> do that though, you can no longer configure it via the management console.
> 
> I was working on a concept of logging profiles that could be assigned to 
> deployments. Though that would still require a change to the deployment. 
> It could be interesting to isolate all deployment logging on-demand. Not 
> quite sure how it would work, but I could see it being useful for debugging.
> 
> On 05/24/2012 03:00 PM, Ales Justin wrote:
>> Can you already configure loggers per deployment?
>> e.g. I want org.hibernate.search at trace for my app, but not for the whole AS
>> 
>> If yes, how?
>> 
>> I mean, is there a better way than adding the old TCCL filter hack I once helped to write. :)
>> 
>> 
>> _______________________________________________
>> jboss-as7-dev mailing list
>> jboss-as7-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev
> 
> -- 
> James R. Perkins
> JBoss by Red Hat
> 
> _______________________________________________
> jboss-as7-dev mailing list
> jboss-as7-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev