Home > Articles > Programming > Java

  • Print
  • + Share This
This chapter is from the book

Building the Architectural Prototype: Part 2

Part 2 of building the architectural prototype for our EJB solution presents a primer on EJB that reviews the callback mechanism, interfaces to the clients, and the transaction support available.

A Primer on Enterprise JavaBeans

As mentioned in Chapters 9 and 11, we need to discuss the lifecycle of the EJB and become a bit more familiar with its architecture. As I stated with the coverage of JSP in Chapter 11, this book can't cover the entire topic, so I refer you to one of the many excellent books on the market today covering EJB for a more thorough presentation (earlier I mentioned Richard Monson-Haefel's Enterprise JavaBeans, published by O'Reilly). However, we can cover the basics here, and most of the readers will get the message.

An Enterprise JavaBean is a component that runs within a container that follows the lifecycle model published in the EJB specification. This lifecycle is managed by the container product that is purchased or downloaded from an open-source organization. There are two different lifecycles, depending on whether the bean is a session EJB or an entity EJB.

Session EJBs are typically used to house utility services and coordination logic in dealing with the entity EJBs. Session beans can do anything they like, even make database calls; however, that is not their intent. There are two types of session EJBs, stateful and stateless. Stateful session beans are guaranteed to have their state persisted between calls from an interested client. A good example of a stateful session bean in Remulak is the bean that manages the shopping cart for an order, UCMaintainOrder. Stateless session beans are just the opposite; their state is completely lost between calls from the client. A good example of a stateless session bean in Remulak is the UCMaintainRltnshp bean. If you guessed that session beans make good use-case control classes, you are absolutely right.

Entity EJBs also fall into two categories: those that implement bean-managed persistence (BMP) and those that implement container-managed persistence (CMP). An entity EJB implemented with BMP will look somewhat similar to what we did in Chapter 11. The bean classes will have several of the callback operations that I mentioned previously (and will cover shortly), but the DAO classes will be almost identical. In the case of an entity EJB that implements CMP, as you will see in the first major coding section in this chapter, the landscape will be drastically different. By different, I mean much smaller. First of all, most call-back operations in the beans will be empty. The best part is that there will be absolutely no DAO classes; you can throw them away.

EJB Callback Mechanism

We have mentioned the callback mechanism already; now it's time to describe it a bit more. The EJB container must have strict control over how your beans behave, both session and entity. This one right that you must give up is payback for the container's being able to manage your transactions and the lifecycle of the bean.

Session beans implement four callback operations that are specified in the SessionBean interface:

  1. ejbActivate(): This operation is called by the container when the bean has been deserialized from passive storage on the server. It allows the bean to reclaim any resources freed during passivation.

  2. ejbPassivate(): This operation is called by the container just before the bean is to be serialized and stored in passive storage on the server. It allows the bean to release any nonserializable resources.

  3. ejbRemove(): This operation is called just before the bean is to be removed from the container and made available for garbage collection.

  4. ejbCreate(): This operation is called whenever a complementary create operation is called on the bean's home interface. It can be used to retrieve values that may apply for the duration of the bean's lifetime.

With session beans, depending on what they are being used for, there may be no implementation code in these required operations of the SessionBean interface. In the case of the UCMaintainRltnshp class, all four will be empty. In the case of the UCMaintainOrder session bean, however, because it is stateful, it has logic in both the ejbCreate() and ejbRemove() operations.

Entity EJBs implement seven different callback operations that are specified in the EntityBean interface:

  1. ejbActivate(): This operation is called by the container when the bean has been deserialized from passive storage on the server. It allows the bean to reclaim any resources freed during passivation.

  2. ejbPassivate(): This operation is called by the container just before the bean is to be serialized and stored in passive storage on the server. It allows the bean to release any nonserializable resources.

  3. ejbRemove(): This operation is called just before the bean is to be removed from the container and made available for garbage collection. In the case of BMP, this is where a SQL delete operation would take place. In the case of CMP, the method is typically empty.

  4. ejbCreate(): This operation is called whenever a complementary create operation is called on the bean's home interface. It can be used to retrieve values that may apply for the duration of the bean's lifetime. In the case of BMP, this is where a SQL insert operation would take place. In the case of CMP, this is where the information originating from the client would be assigned to attributes defined in the bean as abstract public.

  5. ejbPostCreate(): This operation is called immediately after the related ejbCreate() method and is the last place to do initialization work before the client has access to the bean. In the case of BMP and CMP, the methods are typically empty.

  6. ejbLoad(): This operation is called when the container deems it necessary to synchronize the state of the database with the state of the bean. The primary key is taken from the EntityContext object of the bean and not its local attribute. In the case of BMP, this is where a SQL select statement is called. In the case of CMP, the method is typically empty.

  7. ejbStore(): This operation is called when the container deems it necessary to synchronize the state of the bean with the database. In the case of BMP, this is where a SQL update statement is called. In the case of CMP, the method is typically empty.

It should be even more clear now after seeing all the callback method descriptions that with the exception of ejbCreate(), CMP entity beans usually have only business methods. Whether an entity bean is implemented with BMP or CMP can mean the difference of hundreds of lines of codes.

Working with an EJB

For clients to be able to access an EJB, it must work with two interfaces. One is called the home interface, the other the remote interface. Each bean we create then will have three Java classes: classnameBean, classnameHome, and classname. The remote interface is just the class name. All of our hard coding work lives in the classnameBean class.

Both of the interfaces eventually obtain access to the bean for the client. Clients may absolutely never directly access the bean. If this were possible, the container would have lost control of the lifecycle of the bean, rendering all the callback mechanisms useless.

The home interface contains operation stubs to both create and find a bean. These operations are implemented in the bean class. The remote interface is where all the business operation stubs are found. All of these concepts can be made clearer with a few sequence diagrams, as we do next.

EJB Sequence Diagrams

The sequence diagram in FIGURE 12-13 shows the creation and removal of an entity EJB implementing BMP.

FIGURE 12-13 Sequence diagram of BMP creation and removal

The sequence diagram in FIGURE 12-14 shows CMP creation and removal. In both cases, the remote interface is referenced by EJBObject. In addition, the EJBHome, EJBObject, and Container objects are all part of the EJB container. In UML terms, the EJB container is a component that is an active object.

FIGURE 12-14 Sequence diagram of CMP creation and removal

Notice again that the bean instance in the CMP world doesn't do much more than satisfy business method requests.

EJB Transaction Management

Another big advantage to an application's using an EJB container is transaction management. Although you can "roll your own" transaction scheme in the EJB world, it is better if you rely on the container to do it for you. First, it reduces the amount of code that has to be written. Second, it is less error prone.

As with everything else in the EJB environment, transaction control is handled by deployment descriptors. We call this declarative transaction management. Unlike EJB competitors such as Microsoft's COM+ and Component Services framework, the transaction scope can be set at both the bean and the method levels. This is more important than it sounds. Remember that a bean can have both inquiry-type operations and update-type operations. It would be very inefficient to have to establish all the overhead of beginning a transaction just to read information from the database. In all cases with Remulak, container-managed transactions will be the norm.

EJB containers support the transaction types identified in the EJB specification. The various transaction levels are as follows:

  • NotSupported: The transaction scope is not propagated to beans marked NotSupported.

  • Supports: Beans marked Supports will join the transaction scope of another bean already involved in a transaction. However, if the bean is invoked without a transaction scope already established, it runs without a transaction.

  • Required: Beans marked Required must be invoked with transaction already begun or they will create a transaction scope.

  • RequiresNew: Beans marked RequiresNew will always start a new transaction.

  • Mandatory: Beans marked Mandatory must always be part of a client transaction scope. If they are invoked without a transaction already started, the transaction will fail.

  • Never: Beans marked Never must never be invoked with a transaction scope already begun. If they are, the transaction will fail.

These options may seem a bit overwhelming at first, but here comes the good news. If you like the use-case design pattern we have been preaching so far, you will love what it means to transaction settings. All update-oriented operations in the use-case control classes will be marked RequiresNew. All other operations in the use-case control classes will be marked Supports. All other beans can be marked at the bean level as Supports. Because the use-case controller session beans are orchestrating everything, it makes sense that operations that perform updates, such as rltnAddCustomer(), should always start a new transaction. All other beans executed during the transaction just join with the transaction scope that the controller starts. The following is a snippet of the <assembly-descriptor> tag that is part of the ejb-jar.xml file that must be packaged with each deployment:

<assembly-descriptor>
   <container-transaction>
     <method>
        <ejb-name>UCMaintainRltnshp</ejb-name>
        <method-intf>Remote</method-intf>
        <method-name>*</method-name>
     </method>
     <trans-attribute>RequiresNew</trans-attribute>
   </container-transaction>
   <container-transaction>
     <method>
        <ejb-name>UCMaintainRltnshp</ejb-name>
        <method-intf>Remote</method-intf>
        <method-name>rltnCustomerInquiry</method-name>
     </method>
     <trans-attribute>Supports</trans-attribute>
   </container-transaction>
   <container-transaction>
     <method>
        <ejb-name>UCMaintainRltnshp</ejb-name>
        <method-intf>Remote</method-intf>
        <method-name>rltnAddressInquiry</method-name>
     </method>
     <trans-attribute>Supports</trans-attribute>
   </container-transaction>
   <container-transaction>
     <method>
        <ejb-name>UCMaintainRltnshp</ejb-name>
        <method-intf>Remote</method-intf>
        <method-name>rltnRoleInquiry</method-name>
     </method>
     <trans-attribute>Supports</trans-attribute>
   </container-transaction>

The <container-transaction> tag tells the EJB container how to manage the transaction. The <ejb-name> tag identifies the bean, and the next two important tags are <method-name> and <trans-attribute>. Luckily, the EJB specification allows us to indicate a wild-card character—in this case an asterisk (*)—for the method name. This character tells the container to treat all methods of the bean in the same way.

Notice also that we have three additional blocks of <container-transaction> tags. These override the first one. So in effect the tags just mentioned together indicate that all methods in UCMaintainRltnshp will be set to RequiresNew, but rltnCustomerInquiry(), rltnAddress Inquiry(), and rltnRoleInquiry() will be set to Supports. Following the advice already given, the remaining beans in the Maintain Relationships use-case should be marked Supports, as shown here:

   <container-transaction>
     <method>
        <ejb-name>CustomerBean</ejb-name>
        <method-intf>Remote</method-intf>
        <method-name>*</method-name>
     </method>
     <trans-attribute>Supports</trans-attribute>
   </container-transaction>
   <container-transaction>
     <method>
        <ejb-name>AddressBean</ejb-name>
        <method-intf>Remote</method-intf>
        <method-name>*</method-name>
     </method>
     <trans-attribute>Supports</trans-attribute>
   </container-transaction>
   <container-transaction>
     <method>
        <ejb-name>RoleBean</ejb-name>
        <method-intf>Remote</method-intf>
        <method-name>*</method-name>
     </method>
     <trans-attribute>Supports</trans-attribute>
   </container-transaction>
</assembly-descriptor>

With container-managed transactions (not to be confused with container-managed persistence), we don't explicitly commit a unit of work and we don't explicitly roll back a unit of work. The container determines what to do according to the exceptions that are thrown. If no exceptions are thrown, then upon completion of the method that started a transaction (all use-case control classes that are update oriented, in Remulak's case), the transaction will commit.

Anytime RuntimeException, RemoteException, or any exception that inherits from either of these exceptions occurs, a rollback will result. The exception called DAOSysException that was introduced in Chapter 11 inherits from RuntimeException. The other exceptions all inherit from DAOAppException, which inherits from Exception. These are all application errors and won't cause a rollback. A common approach taken to force a rollback when an application exception occurs is to throw EJBException, which inherits from RuntimeException. This is a smart strategy because many application-level exceptions may be able to be corrected, allowing for a recovery.

  • + Share This
  • 🔖 Save To Your Account

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020