Hi,
On Wed, Oct 24, 2012 at 6:45 PM, Steve Lowery <[email protected]> wrote: > I see I can override the AjaxErrorHandlingStrategy in wicket6 to > be AjaxErrorStrategy.INVOKE_FAILURE_HANDLER so that we don't get a 302 to > the appropriate error page (InternalError, NotAuthorized, etc). My > question is how do I do something useful with this? With only that change, > the 500 error comes back to the client and we get a javascript error. This is not new. It is available since 1.5.0. Check http://www.wicket-library.com/wicket-examples/ajax/links?0. The link with 'onFailure' uses this strategy and it shows that the failure handler is actually called. > > We are using ajax and breadcrumbs on our site and what I'd like to do is > hook into the wicket framework so that if one of these errors was detected > on an ajax request, I can simply swap out the "content" portion of the page > with the appropriate error component. That way, the state of the page, > including visited breadcrumbs, navigation menus, etc remain intact, so the > user can hopefully go "back" to some point they were working on by clicking > on one of their breadcrumbs. > > -- > > > IMPORTANT: This e-mail (including any attachments) is intended for the use > of the individual or entity to which it is addressed and may contain > information that is classified, private, or confidential. If the reader of > this message is not the intended recipient, or the employee or agent > responsible for delivering the message to the intended recipient, you are > hereby notified that any dissemination, distribution, or copying of this > communication is prohibited. If you have received this communication in > error, please notify us immediately by replying to this e-mail. Thank you. -- Martin Grigorov jWeekend Training, Consulting, Development http://jWeekend.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
