Many thanks for that!
My pleasure.
Err, if the Appenders and Receivers are bundled in *-db.jar et al then yes we can drop the other webstart jar.
Yes, Appenders and Receivers are bundled in the same jar.
The way I see it working. The user places the -db.jar or jms one in a local directory (the plugin directory) along with the required drivers and any other dependencies. this would mean that the core log4j & chainsaw classes are loaded via the main classloader (which turns out to be the Webstart classloader). The PluginClassloader is a child of this, and can load classes from jars/classes within the Plugin directory. This would mean that the JMSReceiver and DBReceiver classes can be properly loaded and used (I hope).
OK, I see. You are trying to provide a full environment through web-start. IMHO that's a waste of time at best, and in the worst case, a source of confusion and bugs. As I understand it, the idea behind web-start is to provide a self-contained application at click of a URL. If several configuration steps are necessary, you might as well download and launch the application through more conventional means. Anyway, we have discussed this before and I'll go along with whatever you prefer.
configuration is another question entirely, and requires configuring the JMSReceiver or DBReceiver somehow. At the moment there's no way to do that in the GUI, it would have to be via an xml config I believe (I honestly have not tried the DB or JMS Receiver/Appender at all.
Both DBAppender/Receiver can be configured using config files in XML. Of course, you still need the appropriate JDBC drivers. The same holds for JMSAppender/Receiver.
cheers,
Paul Smith
-- Ceki G�lc�
The complete log4j manual: http://www.qos.ch/log4j/
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
