Hi. I'm new to Seam but my company is using the 2.2.1 version of Seam. The
problem is, when the software gets an exception in a call throw a Seam proxy
(JDBC exception in this case, missmatiching field), Seam swallows the
exception and I have to use the debugger to detect that situation.
There is any way to force Seam to show the exception in the logs without
redirecting to another page?
Thanks