- 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: | How is JNDI used to help make JMS applications more portable? |
| A1: | JMS depends on two administered objects: Destination and ConnectionFactory. They are created by the JMS provider administrator, and registered in the JNDI namespace. Later, JMS clients look up the named object in the JNDI and instantiate a resource. This separation between the JMS provider specifics and the JMS API helps make your enterprise application more portable. |
| Q2: | What messaging models are supported by JMS? |
| A2: | Point-to-point (PTP) messaging and publish-and-subscribe (Pub/Sub) messaging. |
-
No Comment
..................Content has been hidden....................
You can't read the all page of ebook, please click here login for view all page.