Re: 1.5 - mapping different error pages for specific errors

2011-05-13 Thread nino martinez wael
Did anything come out of this.. Im looking to utilize the exception
Mapper but I cant find any documentation on it, so do I have to look
in the code to discover the funtionality?

What I basically want todo is to catch a dbconnection exception and
tell the user that there is no connection to the db...

It would also be very helpful with a small example in wicket examples..

regards Nino

2011/5/10 Martin Grigorov mgrigo...@apache.org:
 On Tue, May 10, 2011 at 3:55 PM, nimmy nim_sa...@hotmail.com wrote:
 Hi Martijn,

 I did check out the migration guide but was confused by a reference to a
 non-existing method:

 In Wicket 1.4 it was needed to extend
 org.apache.wicket.RequestCycle.onRuntimeException(Page, RuntimeException).
 Wicket 1.5 gives even better control, by overriding
 org.apache.wicket.Application.newExceptionMapper() it is possible to change
 even the default processing of error pages.

 Will lookup IRequestCycleLister instead.
 Check it and then as a good user add this information to the wiki page ;-)

 Thanks for your help,
 Nim



 --
 View this message in context: 
 http://apache-wicket.1842946.n4.nabble.com/1-5-mapping-different-error-pages-for-specific-errors-tp3511899p3511947.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org





 --
 Martin Grigorov
 jWeekend
 Training, Consulting, Development
 http://jWeekend.com

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org



-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: 1.5 - mapping different error pages for specific errors

2011-05-10 Thread Martijn Dashorst
Check the migration guide, see and read up about IRequestCycleListener

Martijn

On Tue, May 10, 2011 at 3:45 PM, nimmy nim_sa...@hotmail.com wrote:
 Hi,

 How do you map different error pages for specific errors in Wicket v1.5RC2?

 You used to override onRuntimeException in v1.4 but this is no longer the
 case.

 Thanks,
 Nim

 --
 View this message in context: 
 http://apache-wicket.1842946.n4.nabble.com/1-5-mapping-different-error-pages-for-specific-errors-tp3511899p3511899.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org





-- 
Become a Wicket expert, learn from the best: http://wicketinaction.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: 1.5 - mapping different error pages for specific errors

2011-05-10 Thread nimmy
Hi Martijn,

I did check out the migration guide but was confused by a reference to a
non-existing method:

In Wicket 1.4 it was needed to extend
org.apache.wicket.RequestCycle.onRuntimeException(Page, RuntimeException).
Wicket 1.5 gives even better control, by overriding
org.apache.wicket.Application.newExceptionMapper() it is possible to change
even the default processing of error pages.

Will lookup IRequestCycleLister instead.

Thanks for your help,
Nim



--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/1-5-mapping-different-error-pages-for-specific-errors-tp3511899p3511947.html
Sent from the Users forum mailing list archive at Nabble.com.

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org



Re: 1.5 - mapping different error pages for specific errors

2011-05-10 Thread Martin Grigorov
On Tue, May 10, 2011 at 3:55 PM, nimmy nim_sa...@hotmail.com wrote:
 Hi Martijn,

 I did check out the migration guide but was confused by a reference to a
 non-existing method:

 In Wicket 1.4 it was needed to extend
 org.apache.wicket.RequestCycle.onRuntimeException(Page, RuntimeException).
 Wicket 1.5 gives even better control, by overriding
 org.apache.wicket.Application.newExceptionMapper() it is possible to change
 even the default processing of error pages.

 Will lookup IRequestCycleLister instead.
Check it and then as a good user add this information to the wiki page ;-)

 Thanks for your help,
 Nim



 --
 View this message in context: 
 http://apache-wicket.1842946.n4.nabble.com/1-5-mapping-different-error-pages-for-specific-errors-tp3511899p3511947.html
 Sent from the Users forum mailing list archive at Nabble.com.

 -
 To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
 For additional commands, e-mail: users-h...@wicket.apache.org





-- 
Martin Grigorov
jWeekend
Training, Consulting, Development
http://jWeekend.com

-
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org