On Sun, 16 Mar 2003 05:36, Peter Royal wrote: > A "solution" would be to create the LoggerManager for applications in > DefaultLogManager using the application classloader.
Isn't that the problem? I thought that what is happening is that the factory s using the application classloader. So when you load the LogTargetFactory it is loaded from the application classloader and then tried to be cast to the interface defined by the container classloader. We previously enabled this so that users could define their own targets. Anyways I just temporarily disabled this - see if that fixes your problem. > I think this won't > work fully as the application classloader and the container-private > classloader aren't connected at all and thus they won't share a common > view of the interface. If excalibur-logger was broked out into two > jars, one for interface one for impl, the interface jar could go into > the common classloader with the impl only in the container-private > classloader. I don't know if there will be enough benefit to make it > worth the effort. That would be the eventual plan. > Any objections to just moving excalibur-logger.jar back into the common > lib directory? Prefer not - does the above fix the problem. -- Cheers, Peter Donald ----------------------------------------------- | If you turn on the light quickly enough, | | you can see what the dark looks like. | ----------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
