150 JDO exceptions 9.2.7 JDOFatalInternalException This is the
150 JDO exceptions 9.2.7 JDOFatalInternalException This is the base class for JDO implementation failures. instances of this exception should be reported to the JDO vendor. 9.2.8 JDODataStoreException This is the base class for data store exceptions that can be retried. 9.2.9 JDOFatalDataStoreException This is the base class for fatal data store exceptions that cannot be retried. It might be thrown if the data store transaction is rolled back other than at a commit/rollback request by the application. 9.3 Application exceptions The discussion above has centered on JDO exceptions. However, it is also likely that an application will have its own cause to throw and catch domain-specific exceptions. These are referred to as application exceptions. Application exceptions are designed along with the domain model, although they typically end up in a subpackage of the domain package. Domain objects throw and catch these exceptions according to the modeling of business processes by the designer. Persistent instances are capable of throwing and catching the same exceptions as their transient counterparts. No further effort is required of developers in this regard as a result of using JDO for object persistence. What s next? In the following chapter we take a detailed look at the structure of a persistence descriptor. Specific focus is given to the DTD that constrains these XML documents.
Hint: This post is supported by Gama besplatan domen provider