Jacek Laskowski wrote:
While trying to get javax.sql.DataSource <resource-ref>s working it's been noticeable that Jetty emitted only the main message of NamingException with no root cause to a browser.
Would you consider that Jetty emits more detailed exception to a browser?
We have recently changed from Jetty logging (which unwound such exceptions) to commons-logging, which may not. So I'll certainly look at updating the default error page to print more information.
In the mean time you could register a JSP page as the error page for that exception and it will be called with the exception as an attribute, that you can examine and report on that exception within the JSP page.
Also, sometimes Jetty printed out messages with '+'.
This is probably just encoding the messages from the exceptions to make sure that there are no cross-site scripting vulnerabilities by allowing user supplied data to be dispalyed as part of an exception message.
again, post me an example and I'll see if we can improve it.
