Have a look into at the o.a.l.helpers.Loader class. All log4j components use (or should use) the Loader class to load components. Maybe you can tell the Loader class to use your PluginClassLoader. The name PluginClassLoader is a little misleading because it is not just plugins but all log4j components such as Layouts and Appenders etc.
I hadn't thought about the name being a problem. Hmmm, that is a good point. I'll have to have a think about it, but if you have any suggestions on a more appropriate name, let me know.
I'll have a look into the Loader and Joran Actions. Thanks for the pointers. (Altough with or house getting painted, it might take me a while before home is setup to do any work).
You can easily write a joran action which creates an auxiliary classloader to be used in conjunction with o.a.l.helpers.Loader for the length of the Joran configuration session. We can even imagine making using an instance of the Loader class which relies on that auxiliary classloader.
It's kind of a big and intrusive change but one that I am confident should work as long as the config file is customizable by the end user. So, is the log4j.xml file part of the webstart files or is it something supplied by the user?
The configuration file is not part of the web start or any log4j distribution. It's simply a standard log4j.xml file one would normally have, albeit it's used to configure Plugins/Receivers rather than appenders. We, and other users, would like to be able to switch easily between other configurations by choosing an xml file.
thanks for your reply.
cheers,
Paul
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
