Question

In XPages we can define a custom error page that shows whenever a runtime error (500) occurs in an XPages application. However there is a set of errors that ignore this setting (the more fatal ones). So far I know:

• Nesting a custom control inside itself (runs out of stack probably)
• Java security errors

What other errors are there that “break through the error page”?

Answer 1

Errors in the custom error page also generate the Error 500 condition.