Refcards Trend Reports

Platform Engineering: Enhance the developer experience, establish secure environments, automate self-service tools, and streamline workflows

The dawn of observability across the SDLC has fully disrupted standard performance monitoring and management practices. See why.

Apache Kafka: a streaming engine for collecting, caching, and processing high volumes of data in real time. Explore the essentials now.

Data Pipeline Essentials: Dive into the fundamentals of data pipelines and the problems they solve for modern enterprises.

Mike Keith

Architect at Oracle Corp

Ottawa, CA

Joined Dec 2005

Stats

Reputation:	23
Pageviews:	84.8K
Articles:	0
Comments:	10

Refcards
Comments

Nothing here yet! Would you like to post an article?

Refcards

What's New in JPA 2.0

Getting Started with JPA

Comments

JPA 2.0: Why AccessType is Relevant

Feb 27, 2009 · David Green

Personally I believe there is a *LOT* of confusion over the topic ...

Heh. You are right. There is a lot of confusion around this topic, and you seem to be contributing to it! Access type has nothing to do with interception, it determines how state is accessed by the underlying ORM engine. If field access is used then the fields can be accessed reflectively, whereas if property access is used then the property methods are invoked to access the state of the entity. You are bringing in two orthogonal issues, lazy loading and change tracking, and explaining ways that lazy loading can be achieved. That's fine (and you did a reasonable job doing it ;-) but not related to access type.

JPA 2.0: Why AccessType is Relevant

Feb 27, 2009 · David Green

Personally I believe there is a *LOT* of confusion over the topic ...

Heh. You are right. There is a lot of confusion around this topic, and you seem to be contributing to it! Access type has nothing to do with interception, it determines how state is accessed by the underlying ORM engine. If field access is used then the fields can be accessed reflectively, whereas if property access is used then the property methods are invoked to access the state of the entity. You are bringing in two orthogonal issues, lazy loading and change tracking, and explaining ways that lazy loading can be achieved. That's fine (and you did a reasonable job doing it ;-) but not related to access type.

JPA 2.0: Why AccessType is Relevant

Feb 27, 2009 · David Green

Personally I believe there is a *LOT* of confusion over the topic ...

Heh. You are right. There is a lot of confusion around this topic, and you seem to be contributing to it! Access type has nothing to do with interception, it determines how state is accessed by the underlying ORM engine. If field access is used then the fields can be accessed reflectively, whereas if property access is used then the property methods are invoked to access the state of the entity. You are bringing in two orthogonal issues, lazy loading and change tracking, and explaining ways that lazy loading can be achieved. That's fine (and you did a reasonable job doing it ;-) but not related to access type.

JPA 2.0: Why AccessType is Relevant

Feb 27, 2009 · David Green

Personally I believe there is a *LOT* of confusion over the topic ...

Heh. You are right. There is a lot of confusion around this topic, and you seem to be contributing to it! Access type has nothing to do with interception, it determines how state is accessed by the underlying ORM engine. If field access is used then the fields can be accessed reflectively, whereas if property access is used then the property methods are invoked to access the state of the entity. You are bringing in two orthogonal issues, lazy loading and change tracking, and explaining ways that lazy loading can be achieved. That's fine (and you did a reasonable job doing it ;-) but not related to access type.

JPA 2.0: Why AccessType is Relevant

Feb 27, 2009 · David Green

Personally I believe there is a *LOT* of confusion over the topic ...

Heh. You are right. There is a lot of confusion around this topic, and you seem to be contributing to it! Access type has nothing to do with interception, it determines how state is accessed by the underlying ORM engine. If field access is used then the fields can be accessed reflectively, whereas if property access is used then the property methods are invoked to access the state of the entity. You are bringing in two orthogonal issues, lazy loading and change tracking, and explaining ways that lazy loading can be achieved. That's fine (and you did a reasonable job doing it ;-) but not related to access type.

JPA 2.0: Why AccessType is Relevant

Feb 27, 2009 · David Green

Personally I believe there is a *LOT* of confusion over the topic ...

Heh. You are right. There is a lot of confusion around this topic, and you seem to be contributing to it! Access type has nothing to do with interception, it determines how state is accessed by the underlying ORM engine. If field access is used then the fields can be accessed reflectively, whereas if property access is used then the property methods are invoked to access the state of the entity. You are bringing in two orthogonal issues, lazy loading and change tracking, and explaining ways that lazy loading can be achieved. That's fine (and you did a reasonable job doing it ;-) but not related to access type.

JPA 2.0: Why AccessType is Relevant

Feb 27, 2009 · David Green

Personally I believe there is a *LOT* of confusion over the topic ...

Heh. You are right. There is a lot of confusion around this topic, and you seem to be contributing to it! Access type has nothing to do with interception, it determines how state is accessed by the underlying ORM engine. If field access is used then the fields can be accessed reflectively, whereas if property access is used then the property methods are invoked to access the state of the entity. You are bringing in two orthogonal issues, lazy loading and change tracking, and explaining ways that lazy loading can be achieved. That's fine (and you did a reasonable job doing it ;-) but not related to access type.

JPA 2.0: Why AccessType is Relevant

Feb 27, 2009 · David Green

Personally I believe there is a *LOT* of confusion over the topic ...

Heh. You are right. There is a lot of confusion around this topic, and you seem to be contributing to it! Access type has nothing to do with interception, it determines how state is accessed by the underlying ORM engine. If field access is used then the fields can be accessed reflectively, whereas if property access is used then the property methods are invoked to access the state of the entity. You are bringing in two orthogonal issues, lazy loading and change tracking, and explaining ways that lazy loading can be achieved. That's fine (and you did a reasonable job doing it ;-) but not related to access type.

JPA 2.0: Why AccessType is Relevant

Feb 27, 2009 · David Green

Personally I believe there is a *LOT* of confusion over the topic ...

Heh. You are right. There is a lot of confusion around this topic, and you seem to be contributing to it! Access type has nothing to do with interception, it determines how state is accessed by the underlying ORM engine. If field access is used then the fields can be accessed reflectively, whereas if property access is used then the property methods are invoked to access the state of the entity. You are bringing in two orthogonal issues, lazy loading and change tracking, and explaining ways that lazy loading can be achieved. That's fine (and you did a reasonable job doing it ;-) but not related to access type.

JPA 2.0: Why AccessType is Relevant

Feb 27, 2009 · David Green

Personally I believe there is a *LOT* of confusion over the topic ...

Heh. You are right. There is a lot of confusion around this topic, and you seem to be contributing to it! Access type has nothing to do with interception, it determines how state is accessed by the underlying ORM engine. If field access is used then the fields can be accessed reflectively, whereas if property access is used then the property methods are invoked to access the state of the entity. You are bringing in two orthogonal issues, lazy loading and change tracking, and explaining ways that lazy loading can be achieved. That's fine (and you did a reasonable job doing it ;-) but not related to access type.