Do We Need Components for Persistent Data Storage in the Java 2 Enterprise Environment?

Authors:
Stefan Böttcher;Robert Hoeppe
Affiliations:
-;-
Venue:
NODe '02 Revised Papers from the International Conference NetObjectDays on Objects, Components, Architectures, Services, and Applications for a Networked World
Year:
2002

Citing 6
Cited 0

Enterprise Java platform data access

SIGMOD '98 Proceedings of the 1998 ACM SIGMOD international conference on Management of data
Enterprise JavaBean architecture and design issues

ICSE '01 Proceedings of the 23rd International Conference on Software Engineering
J2EE connector architecture and enterprise application integration

J2EE connector architecture and enterprise application integration
Mastering Enterprise Javabeans

Mastering Enterprise Javabeans
Applying model-integrated computing to component middleware and enterprise applications

Communications of the ACM
Java Data Objects

Java Data Objects

Quantified Score

Hi-index	0.00

Visualization

Abstract

Object-oriented applications that use the Java 2 Enterprise Environment (J2EE) and operate on any kind of data storage have to integrate access to persistent data, which is usually achieved by entity beans. However, the use of entity beans as components for persistent data storage has a number of drawbacks. Component level inheritance and dynamic querying are not supported appropriately, and the whole approach seems to be overweight. In order to overcome these weaknesses, we implemented a JCA-compliant resource adapter, which allows the use of Java Data Objects (JDO) instead of entity beans and introduces a lightweight, easy to use and powerful transparent persistence layer for the Java 2 Enterprise Environment.