Ceki,
I guess I am missing the context here since we are successfully configuring plugins today with the old XML configurator.
And looking at the code, the o.a.l.spi.LoggerRepository interface has new methods to get/return the PR associated with it. The Hierarchy class implements them, so there is a reference to the PR. You added these at the time you made PR per-instance instead of a single static. Is there anything more that needs to be done? Are you suggesting that we do away with the PR and move relevant methods into the LoggerRepository?
Yesterday when I wrote
One additional point, a PR knows about its owning LoggingRepository but the inverse is not true. The owning LoggingRepository does not know its PR. This of course makes configuring plugins through a config file impossible.
I looked but somehow did not see that LoggingRepository.getPluginRegistry method. Just ignore the above paragraph.
-Mark
-- Ceki G�lc�
The complete log4j manual: http://qos.ch/eclm
Professional log4j support: http://qos.ch/log4jSupport
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
