You bet. More about exception handling at
http://trailsframework.org/Handling+exceptions, but in short: comment out the exception presenter from your hivemodule.xml
.
Kalle
On 10/15/07, Mark Dzmura <mark.dzmura@...> wrote:
Hi:
In the Trails 1.0 days, many code errors would yield a massive Tapestry stack trace on the screen which gave a pretty good idea what was wrong...
However, my simple Trails 1.1 stuff just fails with [ORG.TRAILS.ERROR
] in the browser, and nothing in the app server log...
Is there a magic switch to be thrown?
Thanks,
Mark