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]
