cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Torsten Curdt" <tcu...@dff.st>
Subject RE: sitemap component selector (was: sub sitemap broken)
Date Tue, 19 Jun 2001 11:10:23 GMT
> I also get the same error by requesting a page from the sub-sitemap with a ?cocoon-reload=true
parameter.
> 
> > What I found out so far....
> > 
> > 1) When I start with a clean repository everything seems to work...
> > 2) Restarting Tomcat a second time shows the bug.
> > 
> > I checked the SitemapComponentSelector. The parent selector is always set
> > - never null. That's really strange!
> > 
> > What's the difference to a clean repository?!

Berin, Giacomo,

I'm really trying to track this down but I need
your guidance...

For my understanding: Where is the need of an hierarchical
ComponentManager when we want to reuse components as good
as possible? When a component is looked up and an instance
is created, the instance is only available to the ComponentManager
(and it's childs) that created it, right? But how does that make
sense? When a component is created in a sub sitemap's ComponentManager
why shouldn't this component also be reused in a different sub sitemap
or the main sitemap? What did I miss to understand ?

In my last working version there was also only ONE ComponentManager
for all sitemaps. My first humbled tries to go back to one ComponentManager
failed. But before wasting time on this maybe one of you guys might
spend a minute and entlighten me ;)
--
Torsten

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


Mime
View raw message