Core J2EE Patterns: Best Practices and Design StrategiesOver 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 / 55
62 ページ
For bean-managed persistence in entity beans, data access code is best
implemented outside entity beans. • See "Separate Data Access Code" on page
113. • See "Data Access Object" on page 390. Caching Enterprise Bean Remote
...
For bean-managed persistence in entity beans, data access code is best
implemented outside entity beans. • See "Separate Data Access Code" on page
113. • See "Data Access Object" on page 390. Caching Enterprise Bean Remote
...
261 ページ
Value Object Context Application clients need to exchange data with enterprise
beans. Problem J2EE applications implement server-side business components
as session beans and entity beans. Some methods exposed by the business ...
Value Object Context Application clients need to exchange data with enterprise
beans. Problem J2EE applications implement server-side business components
as session beans and entity beans. Some methods exposed by the business ...
262 ページ
The client usually requires values for more than one attribute or dependent object
from an enterprise bean. Thus, the client may invoke multiple remote calls to
obtain the required data. • The number of calls made by the client to the
enterprise ...
The client usually requires values for more than one attribute or dependent object
from an enterprise bean. Thus, the client may invoke multiple remote calls to
obtain the required data. • The number of calls made by the client to the
enterprise ...
レビュー - レビューを書く
レビューが見つかりませんでした。
目次
CHAPTER | 7 |
J2EE Platform Overview | 16 |
Design Considerations Bad Practices and Refactorings | 32 |
著作権 | |
他の 16 セクションは表示されていません
他の版 - すべて表示
多く使われている語句
bad practices business components Business Delegate business logic business objects business service business tier BusinessObject Chapter class diagram coarse-grained object Composite Entity composite value object Composite View container create Custom Tag Helper Data Access Code Data Access Object database Delegate pattern dependent objects developers encapsulated enterprise bean entity bean Facade pattern Figure fine-grained Front Controller handling Helper Strategy interactions interface invocation invokes J2EE Pattern Catalog J2EE platform Java Center JDBC JNDI JSP View lookup multiple Presentation Tier problem public class public String public void Refactoring relationships remote method call resource ResourceException ResourceVO response retrieval reuse Sample Code sequence diagram server Service Locator Service to Worker servlet Session Facade shown in Example stateless session bean template Tier Patterns tion transaction typically Value List Handler Value Object Assembler Value Objects Strategy View Helper view management View Strategy