Hello Chris,
We are not catching the
exception in the application, however we are using spring transaction handling
which is proxying our services. I suspect there may be something wrong there. I
will dig into this and let you know.
Thanks for your help,
Shashi
From: eclipselink-users-bounces@xxxxxxxxxxx
[mailto:eclipselink-users-bounces@xxxxxxxxxxx] On Behalf Of Christopher
Delahunt
Sent: Friday, July 02, 2010 7:42 PM
To: EclipseLink User Discussions
Subject: Re: [eclipselink-users] A warning on SQL exception?
Hello Shashi,
EclipseLink should rethrow all exceptions from the database back to the
application, or give the opportunity for the application to intercept them if
an exception handler is registered. Could it be the application or
the server is catching and ignoring them? Are the stack traces from the
exception being printed or is it just the message? If it is being
printed, please send it, and try to look at the calling methods to see if any
of them could be catching and not rethrowing the exception.
Best Regards,
Chris
On 02/07/2010 2:17 AM, Shashikant Kale wrote:
Hi,
We are using eclipselink 1.2.0. I have a basic query
regarding SQL exception.
I found that if any column doesn’t exist in the table or
some primary key already existing in the table, eclipselink shows a warning in
the log, however doesn’t throw any exception back to the calling code. However
this leads to erroneous execution in our programs. Is this something
configurable?
Kindly let me know.
Regards,
Shashi
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-users
