EJB accelerators exist primarily in the middle tier of a J2EE
architecture. Their role is to accelerate the performance of storing data needed
for Enterprise Java Beans (EJBs). By speeding up the performance of the data
storage, the performance of EJBs are accelerated in general. There are four ways that this can be done.
The first way is with a transparent interface such as Java Data Objects (JDO)
coupled with an object database. In this case, there is no need for a mapping
layer because the Java object model is the same model used by the object
database. See transparent
persistence in object databases (new window).
The lack of a mapping layer is show in this diagram.
The second way is with a transparent interface such as Java Data Objects
(JDO) coupled with a relational database. In this case, there is a need for a
mapping layer because the Java object model may not match the model used by the
relational database. Nevertheless, the mapping can be moved to one location as
described in JDO data
conversion (new window). Also see transparent
persistence in object-relational mapping (new
window).
The third way is with a call-level interface such as JDBC coupled with a
relational database. In this case, there is a need for a mapping layer
because the Java object model may not match the model used by the relational
database. The mapping would need to be done at the application level as
described in JDBC data
conversion (new window). Be sure to take a look at
transparent persistence vs. JDBC call-level interface
(new window). This outlines some
disadvantages of using JDBC that you should consider when designing
persistence for J2EE.
Towards the Social Web: Ringside Seats for the Social Big Bang CMSWire, CA - 11 hours ago An early front-runner is what Ringside call its Social Application Server, which ?enables website owners to weave social capabilities directly into existing ...
WSO2 Named ?Cool Vendor? by Leading Analyst Firm Business Wire (press release), CA - 12 hours ago Other key products include the WSO2 Web Services Application Server and WSO2 Enterprise Service Bus, both based on Apache Axis2; WSO2 Web 2.0-enabled ...
Expert One-on-One J2EE Design and Development (Programmer to Programmer) by Rod Johnson Average Customer Review: based on 33 reviews. Customer Review: I thoroughly enjoyed reading this book, particularly well-thought out design guidelines for developing J2EE application with or without EJB. The author introduced several best practices particularly the concepts and usage of Spring and Hibernate based j2ee development is quite helpful. In addition to this book, I find patterns and b...
Core J2EE Patterns: Best Practices and Design Strategies (2nd Edition) (Core Series) by Deepak Alur, Dan Malks, John Crupi Average Customer Review: based on 40 reviews. Customer Review: This book is about using patterns for the J2EE platform, using best practices to design applications that use JSP, Servlet, EJB components, and JMS technologies, preventing reinvention of the wheel when it comes to design and the J2EE platform, and finally identifying bad practices in existing designs and refactoring those designs. ...
Expert One-on-One J2EE Development without EJB by Rod Johnson, Juergen Hoeller Average Customer Review: based on 28 reviews. Customer Review: By now a classic, this book eloquently expressed how the Corba component design committees came up with an EJB specification that was not an ideal cornerstone for all J(2)EE applications. Although very fit for selected purposes the early EJB specs had to evolve to EJB 3 to really leverage the power of Java. Fundamentals of component...
Core Security Patterns: Best Practices and Strategies for J2EE(TM), Web Services, and Identity Management (Core Series) by Christopher Steel, Ramesh Nagappan, Ray Lai Average Customer Review: based on 32 reviews. Customer Review: This is a great book - by far the best security design book for Java and J2EE (including Java SE 6 and Java EE 5) I have read to date. When I first heard about my coworkers talking about this book, I thought "oh great, another J2EE book!" Much to my surprise, this book is not just a how-to security API or patterns recipe book but mu...