[jboss-dev] hibernate 3.3.0 upgrade, slf4j introduction into jbossas

[Ales Justin]

I don't see what you mean. :-)
How could MC help here?

Facade of what kind?
Like we have it now - logging-spi and 2 impls, log4j and jdk - but 
adding new one's?
Meaning all frameworks have to use jboss-logging, which is very very 
thin layer, and with new facades they get the power of any logging 
frmwrk out there?

Or each frmwrk can provide its own thin logging layer, e.g. like Seam 
does, and let MC take care of the injection of the right logging?

David M. Lloyd wrote:
> Well, that's a good project, but bytecode weaving seems like a pretty 
> heavy-duty solution to a simple problem.
> 
> The basic problem is, people (within JBoss and without) are going to use 
> the frameworks they're going to use.  How much effort is it to adapt 
> log2log (which has already run into some interesting technical dilemmas) 
> to another framework, versus just adding another API facade?  It seems 
> like the microcontainer arch would be perfectly suited towards 
> auto-wiring the appropriate logging API.
> 
> Wouldn't it be nice if we could say, "deploy your app in JBossAS/JBossMC 
> and it will *just work*, regardless of what logging frameworks are being 
> used by what"?
> 
> - DML