Comments for developing developer

Comment on Handling Exceptions In Spring MVC – Part 2 by Thusjanthan Kubendranathan

Thusjanthan Kubendranathan — Thu, 11 Jun 2009 01:04:38 +0000

Hi,

Will this intercept HTTP 500 errors as well? I have the exact same setup but it throws a 500 exception:

HTTP Status 500 -

type Exception report

message

description The server encountered an internal error () that prevented it from fulfilling this request.

exception

org.springframework.orm.hibernate3.HibernateSystemException: Provided id of the wrong type. Expected: class java.lang.Integer, got class java.lang.String; nested exception is org.hibernate.TypeMismatchException: Provided id of the wrong type. Expected: class java.lang.Integer, got class java.lang.String
org.springframework.orm.hibernate3.SessionFactoryUtils.convertHibernateAccessException(SessionFactoryUtils.java:659)

For this should I have the setup in web.xml or will this work fine?

Comment on Common Reference Data in Spring MVC by Soongy webOS

Soongy webOS — Mon, 04 May 2009 07:44:07 +0000

thanks

Comment on Handling Exceptions In Spring MVC – Part 1 by Jan

Jan — Thu, 23 Apr 2009 14:55:25 +0000

Nice article
I was wondering about the same question that Srikanta raised:
How does one go about passing a model with additional information to the errorview(s) resolved by the exceptionresolver…?

Well, the only way to create context specific information is to catch the exception, add more information and then re-throw the exception, right?
Some might feel that doing this sort of defeats the purpose of the exceptionresolver… But it still prevents your controller from having to know about the error view.
What I did was to create a model map with the context specific information (just a user-friendly high-level error message actually..) and then add this as a request attribute, which is available in my exceptionresolver override, from where it is easily added to the ModelAndView.

Comment on Handling Exceptions In Spring MVC – Part 1 by Bala

Bala — Mon, 06 Apr 2009 12:30:40 +0000

A good article never seen before!!!!

Comment on Handling Exceptions In Spring MVC – Part 1 by natt

natt — Tue, 17 Mar 2009 15:07:14 +0000

Hi! I have the same problem as Monalisa. I have tried to use the SimpleMappingExceptionResolver but it doesn’t work. What can i do?
Thank you very much.

Comment on Setting the default request format for a Rails app by Taylor

Taylor — Wed, 25 Feb 2009 02:05:35 +0000

Great post. For the public APIs I have been building the users have been sending Content-type application/xml (when sending XML) and Accept text/xml for receiving xml. I respond with YAML by default, eg. in the HTML response block. I may change the default to something like you have shown though because it is more explicit what is happening.

BTW, you can completely disable smilies/emoticons if you wish… I am happy with text version myself

http://codex.wordpress.org/Using_Smilies

I wonder if thinsp would help… : )

Comment on Handling Exceptions In Spring MVC – Part 1 by Monalisa

Monalisa — Wed, 22 Oct 2008 10:49:13 +0000

I’m using the spring exceptionResolver for session expire exception and redirecting to the login page. How can I show a message to the user that the session has expired and then redirect to the login page. Any suggestion is highly appreciated.

Comment on Handling Exceptions In Spring MVC – Part 1 by Josh Kalderimis

Josh Kalderimis — Wed, 09 Jul 2008 18:04:49 +0000

Although, I really do need to finish the 3rd article in this series, once I find a spare moment I will try too (traveling Europe at the moment).

Comment on Handling Exceptions In Spring MVC – Part 1 by Josh Kalderimis

Josh Kalderimis — Wed, 09 Jul 2008 18:02:16 +0000

Hi Nayha,

Why are your filters throwing exceptions? The Spring Exception strategy is only for controllers, so if you can’t stop your filters throwing exceptions, I would put an exception catch in the web.xml for the specific error and general Exception error.

Hope this helps,

Josh

Comment on Handling Exceptions In Spring MVC – Part 1 by Nayha

Nayha — Wed, 09 Jul 2008 15:17:20 +0000

But Spring’s exception handler doesn’t handle exceptions thrown by filters which are called before we hit dispatcher servlet ….. how do we handle them?