Core J2EE Patterns: Best Practices and Design Strategies
Over the last few years, Java 2 Platform, Enterprise Edition (J2EE) technology has emerged and matured as a standard platform for building enterprise applications. While the platform has matured into a solid offering for developing and deploying enterprise applications, it does offer its challenges. As developers, often we confuse learning the technology with learning to design with the technology. In this book, senior architects from the Sun Java Center, Sun's Java consulting organization share with the reader their cumulative design experience with and expertise on J2EE technology.
The primary focus of the book is on patterns, best practices, design strategies, and proven solutions using the key J2EE technologies including JavaServer Pages (JSP), Servlets, Enterprise Java Beans (EJB), and Java Message Service (J.M.S) API. Other ancillary technologies like JDBC and JNDI are also discussed as relevant to their usage in these patterns. The J2EE Patterns catalog with 16 patterns and numerous strategies is presented to document and promote best practices for these technologies.
In addition to the patterns and strategies, the book offers the following:
Core J2EE Patterns delivers:
検索結果1-3 / 22
Facade - Business Entity H - Logic *1 Bean B Logic - B Entity \*/Entity Transaction
Bean Transaction too Bean Logic C Bean managed C OR Container managed |<
-Client or—P-4-Business-> 4-Client or —-4—Business—oPresentation Tier ...
Composite Entity Client Client - o Container / intercepts entity bean calls w Entity
to dependent call is local to entity Transaction Context Transaction — Context
Motivation Entity beans have significantly more overhead than plain Java objects.
An update transaction can resolve conflicts using the time stamp or version
number attribute. If a client holding a stale value object tries to update the entity,
the entity can detect the stale version number or time stamp in the value object