Carsten Ziegeler skrev:
I totally agree that we should avoid object pooling and should in no way introduce this for beans. We have a working pooling implementation for the Avalon components which is transparent (and therefore much better than the original excalibur implementation we use in 2.1.x) and I don't see a need for removing this. As soon as we have moved most of our Avalon components to beans, we could think about removing pooling for Avalon components. So what about deprecating this in 2.2 and removing it with 2.3 or 2.4?
+1
Btw, removing the support for pooled Avalon components might create memory problems as currently resources are freed in the recycle() method.
I see.
/Daniel
