I think if a user throws an exception in a callback outside of a
commit operation, we should simply rethrow it to the user after we
clean up our internal state. Presumably, the specific runtime
exception has meaning to the user's code, and we don't add much
value in wrapping the exception.
I might think differently if the spec allowed/required us to
continue after catching the first exception thrown from a callback,
but it explicitly says that the first exception aborts the
operation. From 3.5.6, "No further lifecycle callback methods will
be invoked after a runtime exception is thrown."
I can go either way on it, but I think Craig's reasoning is sound.
+1
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
