From: [EMAIL PROTECTED]
If we remove the ComponentManagerProxy this problem is solved.
I'm fine with removing the proxy, but can this problem be solved in the
CocoonComponentManager instead? For example by making it aware of the
proxy? Or by making it release the
On Wed, 2003-11-05 at 09:34, [EMAIL PROTECTED] wrote:
From: [EMAIL PROTECTED]
If we remove the ComponentManagerProxy this problem is solved.
I'm fine with removing the proxy, but can this problem be solved in the
CocoonComponentManager instead? For example by making it aware of the
[EMAIL PROTECTED] wrote:
The lookup/release add/remove the component to/from an ArrayList. If you
have a lot of Components which lookup other Components inside the compose
method the List can be really big. If you have a lot of SubSitemaps which
use many InputModules it grows and grows . and
[EMAIL PROTECTED] wrote:
The lookup/release add/remove the component to/from an ArrayList. If you
have a lot of Components which lookup other Components inside the
compose
method the List can be really big. If you have a lot of SubSitemaps
which
use many InputModules it grows and grows
