« Return to Thread: Clueless about error
<convert match="java.lang.Exception" converter="exception"> <param name='include' value='message,lineNumber'/> </convert>
Or allow stack traces too, (which can be useful in development):
<convert match="java.lang.StackTraceElement" converter="bean"/>
Aside from the fact that this is obviously insecure, it can also be quite verbose, so it might be best to use this technique only when the browser and web-server are close together in network terms."
Just to add:
picture the following stack trace:
NumberFormatException java.util.ArrayList
SQLException lsf.com.teste.Class, line 50
I found impossible to get the messages e lineNumbers that relate
specifically to our company packages. Since the project deals with lots of
developers, this approach has been proven useful to us.
To get it we perform an iteration. Do you see any problems with that? Below
goes the example
function errorHandler(msg, ex)
{
if(ex.stackTrace)
{
var stack = ex.stackTrace;
//looking for the specific lsf root package.
for(var i = 0 ; i < stack.length && found = false ; i++)
{
if(stack[i].className.search(/lsf/) >= 0)
{
msgDWR.metodo = stack[i].methodName + "|" + stack[i].lineNumber;
msgDWR.classe = stack[i].className;
found = true;
}
}
}
//do something with msgDWR
}
--
View this message in context: http://www.nabble.com/Clueless-about-error-tp24035958p24041880.html
Sent from the DWR - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@...
For additional commands, e-mail: users-help@...
« Return to Thread: Clueless about error
| Free embeddable forum powered by Nabble | Forum Help |