cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Giacomo Pati <>
Subject Re: cross-reference problem in cocoon 2.1.5 release
Date Sat, 30 Oct 2004 14:25:33 GMT
On Sat, 30 Oct 2004, Steven Gong wrote:

> Vadim, Thank you for your advice!
> But, don't you think if the circular-dependency is supported in
> component container, we can avoid this problem downright? And the
> implementation is not quite difficult. Simply put some signal to tell
> the container not to create an already created component which has
> invoked lookup method in the stack trace.
> Is this right?

The ECM pattern is that lookups should happen where you need the component 
(in the business method) and they should be released as soon as they 
aren't needed anymore. This is because you don't know the implementation 
of the component (ThreadSafe vs. Poolable).

Giacomo Pati
Otego AG, Switzerland -
Orixo, the XML business alliance -

View raw message