Moreover, looking at the code, I wonder if it really useful for this component to be poolable. It does not look like expensive in term of memory/cpu to create an instance of XMLSerializer. Articles as http://www-106.ibm.com/developerworks/library/j-jtp01274.html claims that recycling object is not always a good thing.
It is also something more to take in account when tuning cocoon.
If it were for me, I'd drop the Poolable and Recyclable interfaces *NOW*, but things aren't that easy.
See http://marc.theaimsgroup.com/?t=107640906000001&r=1&w=2 for an interesting thread on the subject.
Ugo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
