cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Carsten Ziegeler <cziege...@apache.org>
Subject Re: CallFunctionNode problems in trunk
Date Fri, 12 May 2006 13:46:26 GMT
Ignore my last email - the current code is correct. The singleton
variable is set to false some lines below :(

Carsten

Carsten Ziegeler wrote:
> Yes, this could be the problem. I briefly looked through the code and
> (i'm not sure) it seems that avalon components without a lifecycle
> interface (threadsafe or poolable) or not treated as SingleThreaded in
> the new Spring based container.
> In line 106 in XmlConfigCreator class in cocoon core we should change from
>                     } else {
>                         current.setModel(ComponentInfo.MODEL_PRIMITIVE);
>                     }
> 
> to
>                     } else {
>                         current.setModel(ComponentInfo.MODEL_PRIMITIVE);
>                         singleton = false;
>                     }
> 
> SVN is currently not working, so I can't commit and I have no time to
> test :( So if someone else could please do this, would be great.
> 
> Carsten


-- 
Carsten Ziegeler - Open Source Group, S&N AG
http://www.s-und-n.de
http://www.osoco.org/weblogs/rael/

Mime
View raw message