From 91dd2d6dc02753b33d1fe1c6c7b366d461b65099 Mon Sep 17 00:00:00 2001 From: Steve Ebersole Date: Sun, 30 Mar 2014 09:45:41 -0500 Subject: [PATCH] document AccessType as topical guide --- .../asciidoc/topical/accesstype/AccessType.adoc | 17 +---------------- 1 file changed, 1 insertion(+), 16 deletions(-) diff --git a/documentation/src/main/asciidoc/topical/accesstype/AccessType.adoc b/documentation/src/main/asciidoc/topical/accesstype/AccessType.adoc index 280aaab5dd..4ddc619a92 100644 --- a/documentation/src/main/asciidoc/topical/accesstype/AccessType.adoc +++ b/documentation/src/main/asciidoc/topical/accesstype/AccessType.adoc @@ -1,8 +1,7 @@ = AccessType :toc: -`AccessType` refers to the JPA notion represented by the `javax.persistence.AccessType` enum. Even though -AccessType is a single value, it actually represents 3 related concepts: +The JPA `javax.persistence.AccessType` enum actually represents 3 related concepts: . Determining which fields/methods constitute a persistent attribute. . Indicating where to look for mapping annotations for each persistent attribute. @@ -30,20 +29,6 @@ FIELD access means that: . At runtime we access the persistent attribute's value directly via the field. - -[sidebar] -.Background --- -Hibernate has always had a notion of "property access strategies" to allow users to control the runtime access part. -But, as back in those days there were no annotations and just XML-based mappings, the other 2 were never a concern. -Initially JPA had no such explicit concept, although it did implicitly define runtime access based on placement of -mapping annotations. JPA 2.0 introduced the concept of `javax.persistence.AccessType` to allow better control over -defining where the persistence provider look for mapping annotations and how it access the attribute values at -runtime. JPA allows defining AccessType at a number of "levels". --- - - - == Implicit (hierarchy) access type The implicit access type for an entity hierarchy defines how access type is defined when there is no explicitly