cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gianugo Rabellino <gian...@apache.org>
Subject Re: Nasty flowscript issue - nailed
Date Tue, 06 Jul 2004 09:52:13 GMT
On Jul 6, 2004, at 11:35 AM, Sylvain Wallez wrote:
>> I changed that to
>>
>>    private String getSitemapPath() throws Exception {
>>         return ObjectModelHelper.getRequest(
>>           
>> EnvironmentHelper.getCurrentEnvironment().getObjectModel()).getSitemap 
>> UR I();
>>     }
>
>
> Aargh! You should absolutely avoid to use the  
> very-internal-and-private EnvironmentHelper class! ContextHelper is  
> your friend ;-)

Good to know, even though this very class is very-internal-and-private  
as well. :-)

>> but being a freshman on Cocoon flow internals, I'm afraid this is  
>> going  to introduce a nasty set of regressions. Can anyone more  
>> knowleadgeable  verify the problem and possibly provide a more clever  
>> solution?
>
> There is a solution, though: there's a different FlowIntepreter for  
> each Processor instance (they are SingleThreaded), and so each  
> interpreter instance could produce a unique identifier and use it as  
> the result of getSitemapPath (which should therefore be renamed).

Any suggestions for a good unique identifier?

Thanks so much,
-- 
Gianugo Rabellino
Pro-netics s.r.l. -  http://www.pro-netics.com
Orixo, the XML business alliance: http://www.orixo.com


Mime
View raw message