On Apr 18, 2007, at 11:05 PM, Paul Smith wrote:
This is because the LoggerRepository is not of type
LoggerRepositoryEx. Chainsaw makes extensive use of the
PluginRegistry, and right now we have no central place where it
can access a PluginRegistry.
What I'll do is create a PluginRegistry somewhere higher up, and
hand this down to the components that need that; bit more IoC
like. I wish I was more IoC aware earlier on.. :)
Hmm, I can see no other way around this than to create a copy of
Hierarchy from log4 1.3, copy that into the component module, and
setup a RepositorySelector during LogUI startup that causes the
default LoggerRepository to become the new Hierarchy version.
Given the naming conflict here, I would suggest we call it
HierarchyEx .. ?
Paul
I've added LoggerRepositoryExImpl to the components which implements
LoggerRepositoryEx with a mix of delegation to an underlying
LoggerRepository, code copied from log4j's 1.3 Hierarchy and fresh
code. Some behavior is degraded, for example, you can register
LoggingRepositoryEventListeners but they will never get called, set
properties but they aren't used in layout. LoggerEventListeners do
get called for the add appender and remove appender, but not level
change. Hopefully what it does implement is sufficient for
Chainsaw's use. If not, let me know what is needed and see if it can
be added to the proxy.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
