Section 1.2 is as follows:
1.2. Final
Entity classes may not be final. No method of an entity class can be
final.
Note
OpenJPA supports final classes and final methods.
This wording is rather confusing. According to section 1. About This
Document, the document provides an overview of the JPA standard. If one
were to assume that the Notes are OpenJPA specific, and the rest is an
overview of the standard, this could be seen as the user's guide saying that
OpenJPA is breaking specs.
In section 2.12. Order By
OpenJPA expands the available ordering syntax. See ??? in the Reference
Guide for details.
In section 2. Entity Lifecycle Management
For a given entity A, the refresh method behaves as follows:
If A is a new entity, it is ignored. However, the remove
operation
cascades as defined below.
If A is an existing managed entity, its state is refreshed from
the
datastore.
If A is a removed entity, it is ignored.
If A is a detached entity, an IllegalArgumentException is
thrown.
The refresh operation recurses on all relation fields of A
whose cascades
include CascadeType.REFRESH.
The problem line is "If A is a new entity, it is ignored. However, the
remove operation cascades as defined below." This could be a copy and paste
mistake from the above discription of the remove method.
--
View this message in context:
http://www.nabble.com/Three-minor-issues-with-the-OpenJPA-User%27s-Guide.-tf3555411.html#a9927486
Sent from the open-jpa-dev mailing list archive at Nabble.com.
