Hi Ceki,
My brain is almost working, just very slowly :-)
A quick scan of the LogManager source and it is obvious!!!!
You associate the LoggerRepository with the application's classloader
when that is created at deployment. I thinks that's what you said
in your last e-mail, I just didn't get it.
The RepositorySelector should be something like:
// Use a weak map for garbage collection of removed deployments
private WeakHashMap repositories = new WeakHashMap();
public associate(ClassLoader cl, LoggerRepository repository)
{
repositories.put(cl, repository);
}
public LoggerRepository getLoggerRepository()
{
// Configured repository?
LoggerRepository result =
repositories.get(Thread.currentThread().getContextClassLoader());
// No repository specified use the default
if (result == null)
result = jbossRepository;
return result;
}
Very nice, very clean, very easy and very powerful :-)
In fact it is so good, it can be used to separate other parts of
JBoss if required. e.g. a user deployed service or the embedded
webserver.
I just need to worry about the form of the configuration...
Regards,
Adrian
_________________________________________________________________
Join the world�s largest e-mail service with MSN Hotmail.
http://www.hotmail.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
