Dec 17th, 2009, 11:36 AM
BeanWrapperFieldSetMapper :: Exception trace missing
We have a situation where we are doing some property editors for converting dates to standard format. Now if the date coming in the file is invalid date, the editor throws an IllegalArgument exception with some default message.
While going through the BeanWrapperFieldSetMapper, it appears that the mapFieldSet method only returns a BindingException with messages in it and ignores the stack trace.
Which is causing to loose the original exception to be handled down the chain.
Is there a better way to do get that exception ?
Last edited by srinivas_vsk; Dec 17th, 2009 at 03:15 PM.
Dec 18th, 2009, 01:23 AM
In 2.0 you just get the messages (but the default format should tell you everything that you need to know to decide what to do with the exception). 2.1 changes the signature of that method to simply throw the aggregate BindException.
Dec 18th, 2009, 09:05 AM
upgraded to 2.1
Last edited by srinivas_vsk; Dec 18th, 2009 at 10:37 AM.