2. Using the Tutorial Examples
3. Getting Started with Web Applications
5. JavaServer Pages Technology
7. JavaServer Pages Standard Tag Library
10. JavaServer Faces Technology
11. Using JavaServer Faces Technology in JSP Pages
12. Developing with JavaServer Faces Technology
13. Creating Custom UI Components
14. Configuring JavaServer Faces Applications
15. Internationalizing and Localizing Web Applications
16. Building Web Services with JAX-WS
17. Binding between XML Schema and Java Classes
19. SOAP with Attachments API for Java
What Is a Message-Driven Bean?
What Makes Message-Driven Beans Different from Session Beans?
When to Use Message-Driven Beans
Defining Client Access with Interfaces
Deciding on Remote or Local Access
Naming Conventions for Enterprise Beans
The Life Cycles of Enterprise Beans
The Life Cycle of a Stateful Session Bean
The Life Cycle of a Stateless Session Bean
The Life Cycle of a Message-Driven Bean
Further Information about Enterprise Beans
21. Getting Started with Enterprise Beans
23. A Message-Driven Bean Example
24. Introduction to the Java Persistence API
25. Persistence in the Web Tier
26. Persistence in the EJB Tier
27. The Java Persistence Query Language
28. Introduction to Security in the Java EE Platform
29. Securing Java EE Applications
31. The Java Message Service API
32. Java EE Examples Using the JMS API
36. The Coffee Break Application
The Contents of an Enterprise Bean
To develop an enterprise bean, you must provide the following files:
Enterprise bean class: Implements the methods defined in the business interface and any life cycle callback methods.
Business Interfaces: The business interface defines the methods implemented by the enterprise bean class.
Helper classes: Other classes needed by the enterprise bean class, such as exception and utility classes.
You package the files in the preceding list into an EJB JAR file,the module that stores the enterprise bean. An EJB JAR file is portableand can be used for different applications. To assemble a Java EE application,you package one or more modules (such as EJB JAR files) into anEAR file, the archive file that holds the application. When you deploy theEAR file that contains the bean’s EJB JAR file, you also deploy theenterprise bean to the Application Server. You can also deploy an EJB JARthat is not contained in an EAR file.Figure 20-2 shows the contentsof an EJB JAR file.
Figure 20-2 Structure of an Enterprise Bean JAR
Copyright © 2010, Oracle and/or its affiliates. All rights reserved.Legal Notices