i just wonder how to map SQLExceptions caused by databaserrors to a
meaningful errormessage for the users.
To be precise:
- my client invokes a method - say updateFields() - on the session bean.
(TX_REQUIRED)
- the sessionbean finds and updates fields of an entity bean. (isModified
Optimization is used)
- the updateFields() method is finished and due to TX_REQUIRED the
transaction is committed and the entitybean is written back to the database.
If an SQLException occurs during the commit of the transaction, all i get
back on the client is a rather cryptic RolledbackException. I see no
possibilty to drill down to the causing SQLException and display a useful
message to the user. (e.g. unique index violation)
How do the experts solve this?
Thanx for your help.
Albert
*******************************************************************
DELICom DPD Deutscher Paket Dienst GmbH & Co. KG
Wailandtstrasse 1, D-63741 Aschaffenburg
Telefon: +49 / (0)6021 / 492-6039
Fax: +49 / (0)6021 / 492-6502
E-Mail: [EMAIL PROTECTED]
Internet: http://www.dpd.de
*******************************************************************
----
To unsubscribe, send email to [EMAIL PROTECTED] and
include in the body of the message "unsubscribe jonas-users".
For general help, send email to [EMAIL PROTECTED] and
include in the body of the message "help".
