Re: [Wicket-user] Exception Strategy in 1.3

* craigdd: Thanks Eelco, your example was extremely helpful and I agree that the API is not obvious when it comes to this type of stuff. It also doesn't help when the javadoc for RequestCycle.onRuntimeException refers to DefaultExceptionResponseStrategy which does not exist in 1.3. I just

Re: [Wicket-user] Exception Strategy in 1.3

this sure seems familiar. didn't we have a nice plan to address this a few months back? Eelco Hillenius wrote: You can return the page you want to be displayed and have full control. I know the API currently is non-obvious; I complained about this in another thread. For example, this

Re: [Wicket-user] Exception Strategy in 1.3

On Wednesday, May 23, 2007, 2:53:50 AM, craigdd [EMAIL PROTECTED] wrote: Thanks Eelco, your example was extremely helpful and I agree that the API is not obvious when it comes to this type of stuff. It also doesn't help when the javadoc for RequestCycle.onRuntimeException refers to

Re: [Wicket-user] Exception Strategy in 1.3

Will do Gwyn, I plan on spending a few hours tonight to see what type of update to the API would be needed to help out my type of situation. -Craig Gwyn wrote: On Wednesday, May 23, 2007, 2:53:50 AM, craigdd [EMAIL PROTECTED] wrote: Thanks Eelco, your example was extremely helpful and I

Re: [Wicket-user] Exception Strategy in 1.3

As far as i know the wicket session is mandatory in wicket but that does not mean you have to use it to store information. Other then that i see no reason why your proposed strategy should not work. Maurice On 5/22/07, craigdd [EMAIL PROTECTED] wrote: Basically what I want to do is set the

Re: [Wicket-user] Exception Strategy in 1.3

* craigdd: I'm wondering if there are any other hooks that I can implement that leaves the respond method alone but have the exception and internal page available. Have a look at ExceptionErrorPage and IExceptionSettings -- Jean-Baptiste Quenot aka John Banana Qwerty

Re: [Wicket-user] Exception Strategy in 1.3

Make a subclass of WebRequestCycle, and override onRuntimeException(). Works like a charm for me. 2007/5/22, craigdd [EMAIL PROTECTED]: True the wicket session is mandatory, thanks for pointing that out. As for my question though, I'm looking for the best way to implement this strategy. I

Re: [Wicket-user] Exception Strategy in 1.3

Overriding the onRuntimeException does not work because you don't have access to the page that you are directing to. The page parameter in this method if the context from where the exception was thrown. -Craig Rüdiger_Schulz wrote: Make a subclass of WebRequestCycle, and override

Re: [Wicket-user] Exception Strategy in 1.3

You can return the page you want to be displayed and have full control. I know the API currently is non-obvious; I complained about this in another thread. For example, this is what I'm using for the project I'm working on: public Page onRuntimeException(Page page, RuntimeException

Re: [Wicket-user] Exception Strategy in 1.3

Thanks Eelco, your example was extremely helpful and I agree that the API is not obvious when it comes to this type of stuff. It also doesn't help when the javadoc for RequestCycle.onRuntimeException refers to DefaultExceptionResponseStrategy which does not exist in 1.3. Thanks Craig Eelco

Re: [Wicket-user] Exception Strategy in 1.3

Basically what I want to do is set the internal error page to my own internal page, i.e. my login page, and add a message from the a resource bundle, .properties file, that includes an error code that is generated from an internal RuntimeException. Another requirement is that a Session is