Entity Beans provide both data persistence and the possibility of caching objects and data in the middle-tier. The EJB 1.1 specification has three commit options which determine how EJBs are cached across transactions: Option C pools objects without identity; Option B caches objects with identity; Option A caches objects and data. This paper explores the impact on performance of these different commit options, pool and cache sizes on a realistic application using the Borland Application Server.
CITATION STYLE
Brebner, P., & Ran, S. (2001). Entity bean A, B, C’s: Enterprise java beans commit options1 and caching. In Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics) (Vol. 2218, pp. 36–55). Springer Verlag. https://doi.org/10.1007/3-540-45518-3_3
Mendeley helps you to discover research relevant for your work.