Hi! Yes, I'll change the one in trunk as well today.
It's funny, because I only use the ContentAggregator, the XMLSerializer and the FileGenerator. I have to investigate a little more in which configuration this actually happens, but I am fairly sure that the ContentAggregator (the only place where a SitemapSource is used) releases everything correctly. Since this only seems to happen when an Exception is thrown during processing, I thought that maybe there is an error deeper in the error handling code. Something like a missing finally... The error is rather hard to notice because if you use "cocoon servlet", it actually doesn't show it. I noticed it in my little test project. I hope it's again something I did wrong, I'll keep you guys up to date. max > -----Original Message----- > From: Carsten Ziegeler [mailto:[EMAIL PROTECTED] > Sent: Wednesday, March 22, 2006 09:59 > To: [email protected] > Subject: Re: error handling causes NPE? (was: error handling in > aggregations) > > > Max Pfingsthorn schrieb: > > Hi! > > > > Err, guys, can it be that the sources aren't released > correctly after a ProcessingException during pipeline > execution? I get the same NPE I did when I didn't release a > sitemap source correctly a while ago after I apply this patch > to 2.1.8... > > > > Any ideas? > > > Usually the pipeline components release the sources in their recycle() > method. > So could it be that you have a buggy component in your pipeline? > > PS: Can you apply your changes to the ContentAggregator to trunk as > well, please? > > Carsten > > > -- > Carsten Ziegeler - Open Source Group, S&N AG > http://www.s-und-n.de > http://www.osoco.org/weblogs/rael/ >
