All, Is there any relatively easy way to keep Cocoon from essentially "swallowing" error messages into the [xmlui]/WEB-INF/logs/handled-errors.log when using the XMLUI?
I'm noticing we've had a recent Java-level error (a java.lang.NullPointerException) that never made it to the normal [dspace]/log/dspace.log file. Instead, Cocoon swallowed it and logged them to the 'handled-errors.log', since it also resulted in a sitemap error. I'd love to ensure these errors also get logged to dspace.log via log4j, so that there is a single log file to monitor for such errors. Any ideas? Admittedly, I haven't dug around in Cocoon logging to see if there's something that can be changed in the sitemap to support this. It just seems like this is something we should fix in the out-of-the-box DSpace, so that we don't have to point people to multiple error files for the XMLUI. - Tim -- Tim Donohue Research Programmer, IDEALS http://www.ideals.uiuc.edu/ University of Illinois [email protected] | (217) 333-4648 ------------------------------------------------------------------------------ Open Source Business Conference (OSBC), March 24-25, 2009, San Francisco, CA -OSBC tackles the biggest issue in open source: Open Sourcing the Enterprise -Strategies to boost innovation and cut costs with open source participation -Receive a $600 discount off the registration fee with the source code: SFAD http://p.sf.net/sfu/XcvMzF8H _______________________________________________ Dspace-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-devel
