Re: [future-showstopper] Sitemap reload & dispose() & NPEs

[Ovidiu Predescu <ov...@cup.hp.com>]

I believe I am possibly affected by the same bug. I did an update to
get the old jars again (the ones you put in the repository), but the
problem didn't go away.

The problem I have is with an ComponentSelector which doesn't seem to
pass the ComponentManager to the components added to it using
addComponent. Do you think this is the same problem?

Thanks,
Ovidiu

On Wed, 20 Mar 2002 00:31:10 -0500, "Vadim Gritsenko" <va...@verizon.net> wrote:

> Hi,
> 
> I was playing with our almost-released Cocoon, and found quite serious
> bug in component management, in the Excalibur. At least, after replacing
> the excalibur with the older version, bug goes away.
> 
> Symptoms:
>  - Disposed XSLT transformer by component manager as part of sitemap
> handler disposal in the sitemap Manager regenerate, AND TraxTransformer
> with the instance of this XSLT transformer without any knowledge of
> what's going on (net result: NPE);
>  - NPE in ContentAgregator were it never was observed before while
> browsing documentation;
>  - Main sitemap is regenerated without reason (!) when there is first
> access to the sub sitemap, and both sitemaps were already compiled;
> ... and other weird things.
> 
> After some investigation I decided just to fallback to well-tested and
> known-to-be-working Excalibur version. All weird things went away. I'm
> happy, puzzled, tired.
> 
> 
> Vadim
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
> For additional commands, email: cocoon-dev-help@xml.apache.org
> 
> 

---------------------------------------------------------------------
To unsubscribe, e-mail: cocoon-dev-unsubscribe@xml.apache.org
For additional commands, email: cocoon-dev-help@xml.apache.org