cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Carsten Ziegeler" <cziege...@s-und-n.de>
Subject RE: Bug? Foreign SourceResolver in Generator.configure()
Date Fri, 11 Jun 2004 10:01:41 GMT
Reinhard Poetz wrote:
> 
> Carsten Ziegeler wrote:
> 
> >Thanks Vadim for the test case.
> >
> >Ok, we have a minor problem here :)
> >
> >The contract of the SourceResolver is that it always 
> resolves relative 
> >to the *current sitemap*. The interesting question now is: 
> what is the 
> >"current sitemap" for a component that is instantiated? Is it the 
> >sitemap the component is declared in or the sitemap of the current 
> >request?
> >Now, I tend to the first option. If this is the case we have a bug :(
> >
> >To be precise I think we have this behaviour in Cocoon since 2.1.0.
> >I just tested 2.1.5 and the problem exists there as well.
> >
> >The problem is that the lookup and therefore the 
> initialization of the 
> >generator is started from the sub sitemap and the sub 
> sitemap of course 
> >runs in the context of the location of the sub sitemap.
> >
> >Now, we could solve this by "surrounding" the initialization 
> phase of a 
> >component with a change of the current context. So, all init 
> methods of 
> >a component run in the context of the sitemap where the component is 
> >defined. All other methods run in the context of the sitemap 
> where the 
> >component is used.
> >
> >WDYT?
> >  
> >
> 
> Sounds to be the solution that is expected by the user.
> 
Yes, the problem imho is that it "sounds" this way. Although this
bug is in Cocoon since years, noone complained about it until
recently - so either noone needed it until now or the current
way (the "bug") is the way user expect it :)

Carsten


Mime
View raw message