Hi Timm, yep, unfortunately there is already a lot of code around which instead of rethrowing the exception, or wrapping it in a somehow cascading exception, simply throw a new exception using the message of the original exception. In my experience, a message "null" means a null pointer exception happened, a message " 3 <= 1" means an ArrayIndexOutOfBounds, a message "Index: 2, Size: 1" means a collection index out of bound, the name of a class means either a class cast exception or a class not found exception.
Anyway, if you are using an IDE, you can put a breakpoint on the line where the non-cascading exception is being rethrown, and from there look at the real exception, the one on which the code is simply calling e.getMessage() without giving any other intresting information. Or even modify the throw to use a cascading exception and send the patch to the authors of Jasper :) Simone timm.f wrote: >Hi Simone, > >thank you for your answer. You are right, that it is a problem with the >JSP-Page. The database schema from which the JSP gets its data has been >changed and I didn't know this. If it had been a cascading exception message >it would have been easier to analyze. > >Thank you. >Timm > >-- >View this message in context: >http://www.nabble.com/JasperExeption-t1563543.html#a4247786 >Sent from the Cocoon - Users forum at Nabble.com. > > >--------------------------------------------------------------------- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > -- Simone Gianni --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
