On Thu, 6 Sep 2001 22:52, Berin Loritsch wrote:
> Leo Sutic wrote:
> > Jörn,
> >
> > the crux is the compilation of the sitemap. The sitemap compiles to
> > org.apache.cocoon.www.sitemap_xmap for *all* webapps. Since the sitemap
> > class is loaded using the same classloader as cocoon (since you put the
> > libs in the Resin lib directory), the same class gets loaded for
> > different webapps.
>
> Actually, you are also experiencing issues with the classloader (for
> instance, the cross polination of log events. I will post this issue on
> the Avalon-dev list. Hopefully, with Giacomo's LogKitManager this can be
> dealt with. Cocoon does not do anything special with the LogKit Hierarchy
> to force different roots or default loggers for different contexts. This
> could also be taken care of with a classloader solution I proposed a while
> ago.
>
> TO THE AVALON TEAM:
>
> LogKit is cross-polinating log events to log targets that belong in another
> web context. The change in configuration is that LogKit is now loaded in a
> base ClassLoader, and not in the unique ClassLoaders that are used for web
> apps. The result is that the Heirarchy object is shared between all
> contexts. We need a way to enforce all Contexts to be separate.
Fixed in CVS. Each LogKitManager now works on a private hierarchy.
--
Cheers,
Pete
*--------------------------------------------------*
| Wise men don't need advice. Fools don't take it. |
| -Benjamin Franklin |
*--------------------------------------------------*
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
