Some receivers available via Chainsaw have third party jar dependencies (for example: DBReceiver, CustomSQLDBReceiver, VFSLogFilePatternReceiver).
Chainsaw is available via Web Start, and to support those receivers with third party jar dependencies, we needed to provide a mechanism to load those classes. The mechanism we chose was to create a custom classloader which can load classes from any jar in the $user.dir/.chainsaw/plugins directory. To use a receiver with third party jar dependencies: - define the receiver in your Chainsaw config file (see an example from Chainsaw's Welcome tab) - launch Chainsaw - check the 'ok to remove security manager' box in Chainsaw's application-wide preferences screen - point the 'automatic configuration URL' application-wide preference to your Chainsaw config file's URL - exit Chainsaw - copy third party jar dependencies to $user.dir/.chainsaw/plugins - launch Chainsaw Scott -----Original Message----- From: C. Benson Manica [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 30, 2006 11:12 AM To: log4j-user@logging.apache.org Subject: Fixing pluginDirectory (I'm trying a different tack on this question, because I feel certain that there is a simple answer to my problem and it is driving me insane.) When I run Chainsaw, I get this error: pluginDirectory cannot be null, and it must exist and must be readable, using the normal Classloader What exactly is the pluginDirectory? How do I set it up? Will the receivers I define in the chainsaw configuration XML work when I do? How can I figure out what value is being used as the pluginDirectory that causes this error? -- C. Benson Manica ataru(at)sdf.lonestar.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
