0
votes

I am using this brilliant piece of code to get the stacktrace in a custom error page

var  stackTrace = "";
    var  trace = requestScope.error.getStackTrace();
    for (var  i = 0; i < trace.length; i++){
    stackTrace += trace[i]+ "<br />" ;
}
return  stackTrace;

But it seem like this is not returning any extlib errors The following fault is only seen if I use the default runtime error page:

"Invalid component id dynC for partial refresh"

any way to modify my code to also return the extlib errors?

1
I'm not sure what you mean by not returning extlib errors. The "invalid component id for partial refresh" error is a core runtime bug... what errors are you expecting to be reported that aren't?Tim Tripcony
Why aren't you using remote debugging capabilities instead of writing your stacktrace to the console? mindoo.de/web/blog.nsf/dx/20.07.2010094952KLEB7R.htmjjtbsomhorst
@Tim this message "Invalid component id dynC for partial refresh" (dynC is dynamic content control in extlib) is reported if I use the default runtime error page. but not if I use the code aboveThomas Adrian
@jjtbsomhorst don't know what you mean, I am not writing anything to the consoleThomas Adrian
I guess my point is that your question asks how to return extlib errors, but the error you're referring to has nothing to do with the Extension Library. Anytime you fire a partial refresh event, and the refreshId attribute of that event specifies a component ID that doesn't exist, you'll get the error you're receiving... whether or not the Extension Library is even installed.Tim Tripcony

1 Answers

0
votes

It depends on what kind of exception is throwed. Not all exceptions have a 'getStackTrace()'. See here for more info about Xpages error management: http://www-10.lotus.com/ldd/ddwiki.nsf/dx/error-management-in-xpages.htm. Take a look at the comment from "Dominykas Kardokas" on that page.