- 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: | In which tier should I implement the referential integrity constraints? |
| A1: | It's generally best to implement referential integrity constraints logic in the EIS tier rather than the EJB tier. Implementing the constraints in the EIS tier means that they can be used by non-J2EE applications and offer greater performance and reliability. Implementing such constraints in the EJB tier duplicates logic and makes maintenance difficult. On the other hand, EIS tier constraints such as database procedural triggers are not portable across database vendors. |
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.