cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stuart Roebuck < (BlueYonder)>
Subject Re: [C2] Possible bug in ?
Date Wed, 01 Aug 2001 20:07:54 GMT

On Wednesday, August 1, 2001, at 08:10  pm, Vadim Gritsenko wrote:

> Stuart,
> </snip>
>> A request for "new-test_news.html" is going to request
>> "cocoon:/select/news/test_news.xml" which, during its processing is going
>> to look for JaxpTransformer components from its own pool before that of
>> its parent.  Consequently, on every call it is going to create a whole 
>> new
>> pool and set of transformers.
> SitemapComponentSelectors (and their pools) are created once during 
> initialization
> of (sub)sitemap, and parent is set to appropriate 
> SitemapComponentSelector from the
> parent sitemap (or Cocoon itself for main sitemap), see 
> AbstractSitemap.compose() method.
> When looking for component, first component from this sitemap is looked 
> up. If none found,
> selector attempts to get component from parent.
> Are you able to reproduce your problem on Cocoon's example sitemap?

I can't quite tell from your response whether you are proving me wrong or 
encouraging me to investigate this further.  If the first then your 
probably right, blind debugging of totally unfamiliar code isn't easy 
(particularly when it is practically undocumented) and you sound like you 
know it a lot better than me; if the second then please let me know so 
that I know it's worth pursuing.

I do know that something is causing requests for the same page to create 
16 new JaxpParser components on every invocation, and my posts are an 
attempt to move toward finding a solution.


Stuart Roebuck                        
Lead Developer                               Java, XML, MacOS X, XP, etc.
ADOLOS                                           <>

To unsubscribe, e-mail:
For additional commands, email:

View raw message