> 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 requestlifecyclecomponent via its originating component manager? It's just that we *do* have that code in there, and if you remove it, someone else will pipe up and say that "oh, why oh why did you break my application?". So I'm trying to find a solution that will fix the problem (and it is a problem), byt leaves ECM intact. /LS --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
