Tracking down a problem moving from 2.2 -> 2.3 I noticed buried in the turbine.log file that an exception had been thrown by one of my tools that was called from Velocity code.
Is there any way to handle tool exceptions? I consider any exception that escapes from a tool a serious problem and would prefer to show an error page rather than continuing with a null result from the tool. I searched the archives and found the same question asked in 2001 but no responses. -- Sam Solon [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
