[
https://issues.apache.org/jira/browse/JDO-552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12543429
]
Craig Russell commented on JDO-552:
-----------------------------------
This is by design. The rationale for having a failed object is that this is the
object that was responsible for the exception, and the assumption is that once
an object has an exception for the current operation, it is considered failed
and no further action is taken.
The rationale for a Throwable[ ] is that many JDO operations act on multiple
objects, and each object might have a different reason for failing. So the
pattern is that each object is attempted and if it fails, the exception is
added to the Throwable[ ].
Can you give an example where you would have a failed object that was not one
of the failed objects in the Throwable[ ]?
> JDOFatalDataStoreException, JDOObjectNotFoundException and
> JDOOptimisticVerificationException dont allow nested exceptions and failed
> objects together
> ------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JDO-552
> URL: https://issues.apache.org/jira/browse/JDO-552
> Project: JDO
> Issue Type: Improvement
> Components: api2
> Reporter: Erik Bengtson
> Priority: Trivial
>
> These 3 exceptions have constructors (String msg, Throwable[] ex) and (String
> msg, Object failedObject), but dont have a (String msg, Throwable[], Object
> failedObject)
> JDOFatalDataStoreException
> JDOObjectNotFoundException
> JDOOptimisticVerificationException
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
