[WICKET-3806] Remove the possibility to configure ExceptionMapper

• Type: Task
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 1.5-RC4
• Fix Version/s: 1.5-RC5
• Component/s: wicket
• Assignee: Martin Tzvetanov Grigorov
• Reporter: Martin Tzvetanov Grigorov
• Created: 16/Jun/11 19:38
• Updated: 16/Jun/11 19:40
• Resolved: 16/Jun/11 19:40

Description

Currently there are two ways to react on thrown exception - ExceptionMapper and IRequestCycleListener#onException().
Users should use IRequestCycleListener#onException(). The exception mapper is used as last resort when the exception is not recognized by Wicket to show the configured internal error pages.
With this ticket we will remove the possibility to configure custom ExceptionMapper.

Discussed with Igor in IRC.