|
||||||||
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
_______________________________________________ logback-dev mailing list logback-dev@qos.ch http://mailman.qos.ch/mailman/listinfo/logback-dev
Since the context is the registry point, we must ensure that the existing code which uses OptionHelper to instantiate objects has access to the context. My little investigation shows this to be the case. So we are good.
There is also the Loader.loadClass(String classname, Context context) used to load classes. It is used by NestedComplexPropertyIA which is a rather important class used to load most logback components other than appenders. So can we get away by making *just* class loading pluggable or is also object creation need to be pluggable?