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 / 73
298 ページ
Data Access Object Strategy The Session Facade can directly use one or more
DAOs to represent the business data. This is done when the ... A Session Facade
encompasses the interactions between the client and the business components.
Data Access Object Strategy The Session Facade can directly use one or more
DAOs to represent the business data. This is done when the ... A Session Facade
encompasses the interactions between the client and the business components.
300 ページ
Because of the Session Facade's coarse-grained access, it is easier and more
manageable to define security policies at this level rather than at the participating
business component level. Business components offer fine-grained control points
...
Because of the Session Facade's coarse-grained access, it is easier and more
manageable to define security policies at this level rather than at the participating
business component level. Business components offer fine-grained control points
...
340 ページ
be an additional performance overhead on the client due to the construction
process. In addition, the client must contain the business logic to manage the
relationships between the components, which results in a more complex, larger
client.
be an additional performance overhead on the client due to the construction
process. In addition, the client must contain the business logic to manage the
relationships between the components, which results in a more complex, larger
client.
レビュー - レビューを書く
レビューが見つかりませんでした。
他の版 - すべて表示
多く使われている語句
asynchronous blockout business components Business Delegate business logic business objects business service business tier BusinessObject class diagram coarse-grained object Composite Entity composite value object Composite View context corepatterns create Custom Tag Helper Data Access Object database Delegate pattern dependent objects EJBHome encapsulated enterprise bean entity bean Facade pattern Factory Figure FilterChain Front Controller handling HttpServletRequest implementation interactions interface invocation invokes J2EE platform Java Java Center JavaBean javax JDBC JNDI lookup multiple º º Pattern Pattern Presentation Tier processing Project public class public String public void Refactoring relationships RemoteException resource ResourceVO response Sample Code sequence diagram server Service Locator Service to Worker ServiceLocator servlet Servlet Exception Session Facade shown in Example solution stateless session bean template throws Tier Patterns Tier Tier tion transaction typically update Value List Handler Value Object Assembler Value Objects Strategy View Helper view management