Unico Hommes wrote:
Vadim Gritsenko <vadim <at> reverycodes.com> writes:
Yep, again this same ol' NPE from SourceResolver:
<snip/>
This is probably due to the fact that SourceResolver was disposed before TreeProcessor. Every once in a while we run into this limitation that ECM does not support any type of dependency management and shutdown order control.
I'd swallow the NPE in TreeProcessor since the contract in ECM seems to be that
dependent components might already have been disposed of.
Why in tree processor and not in CocoonComponentManager itself? Otherwise, you'd end up with hunting down all manager.release() statements and wrapping them in the try/catch block - otherwise you can't be sure will release() work or throw an exception.
Vadim
