- Copyright
- About the Authors
- Acknowledgments
- We Want to Hear from You!
- Introduction
- Enterprise Java Architecture
- Understanding EJB Architecture
- Understanding EJB Types and Interfaces
- Enterprise JavaBean Types
- Enterprise JavaBean Under the Hood
- EJB Interfaces
- Java Remote Method Invocation over Internet Inter-ORB Protocol Technology
- Remote and Local Interfaces
- Deployment Descriptors
- Packaging and Deploying Enterprise JavaBeans
- Enterprise JavaBean Restrictions
- Best Practices
- Summary
- Q&A
- Quiz
- Exercises
- Understanding Session Beans
- Using JNDI for Naming Services and Components
- Developing Stateless Session Beans
- Developing Stateful Session Beans
- Designing Web Applications
- Entity Beans and Message-Driven Beans
- Understanding Entity Beans
- Using JDBC to Connect to a Database
- Developing Bean-Managed Persistence Entity Beans
- Developing Container-Managed Persistence Entity Beans
- Developing Container-Managed Relationships
- Examining Container-Managed Relationships
- Implementing Container-Manager Relationships
- Designing Container-Managed Relationships
- Defining the Home Interfaces
- Defining the Remote Interfaces
- Implementing the Enterprise Bean Classes
- Declaring the Deployment Descriptors
- Writing a Client
- Packaging and Deploying the Enterprise Beans
- Running the Example
- Best Practices
- Summary
- Q&A
- Quiz
- Exercises
- Understanding JMS and Message-Driven Beans
- Developing Message-Driven Beans
- Looking Under the Hood of an MDB
- Designing the Message-Driven Bean
- Implementing the Enterprise Bean Class
- Declaring the Deployment Descriptor
- Writing a Client
- Packaging and Deploying the Enterprise Bean
- Running the Example
- Examining the Life Cycle of a Message-Driven Bean
- Best Practices
- Summary
- Q&A
- Quiz
- Exercise
- Advanced EJB Applications
- Appendixes
- Index
Q&A
| Q1: | What are the main tiers of the J2EE architecture? |
| A1: | The J2EE architecture consists of four tiers: the client tier, presentation tier, business logic tier, and the EIS tier. |
| Q2: | Why should I use design patterns? |
| A2: | Design patterns are reusable artifacts, and proven solutions that can be directly applied to solve certain problems. Design patterns are gained by experience and documented for use by architects and designers of enterprise applications. |
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.