Home > Articles > Programming > Java

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

Creating a BMP Implementation

It may seem awkward that we started with what might seem like a very hands-on implementation in Chapter 11, followed by the very hands-off implementation that CMP provides, only to end with another relatively hands-on implementation with BMP. But there's a reason. I firmly believe that as the EJB vendor community embraces the EJB 2.0 specification, and in particular its support for a common CMP standard, fewer projects will choose BMP as a solution. It may be necessary sometimes, but lifting the burden of writing and managing SQL calls from the project team eliminates at least 20 to 25 percent of the effort. It also shortens the testing cycle; the ripple effect is exponential.

Let's examine what is necessary to make the Maintain Relationships use-case a BMP implementation. Much of the work is already done for us. Here are the relevant issues:

  • The work that was done to RemulakServlet, the JSPs, and the UCMaintainRltnshp use-case controller to support the enhanced CMP implementation remains the same for BMP.

  • The entity beans using CMP require substantial changes, but in structure only, to support BMP. Modified versions of the DAO classes introduced in Chapter 11 will be required to handle the SQL interaction with the database.

The changes boil down to adding calls to the DAO classes within the appropriate callback methods. Let's start by looking at CustomerBean as a BMP entity:

package com.jacksonreed;
import java.io.Serializable;
import java.util.Enumeration;
import java.util.Vector;

import java.util.Collection;
import javax.ejb.CreateException;
import javax.ejb.DuplicateKeyException;
import javax.ejb.EJBException;
import javax.ejb.EntityBean;
import javax.ejb.EntityContext;
import javax.ejb.FinderException;
import javax.ejb.NoSuchEntityException;
import javax.ejb.ObjectNotFoundException;
import javax.ejb.RemoveException;
import java.rmi.RemoteException;
import javax.naming.InitialContext;
import javax.naming.NamingException;
import javax.sql.DataSource;
import java.util.List;
import java.util.Iterator;
import java.util.ArrayList;

public class CustomerBean implements EntityBean {

   final static boolean VERBOSE = true;

   private EntityContext ctx;

   private Integer customerId;
   private String customerNumber;
   private String firstName;
   private String middleInitial;
   private String prefix;
   private String suffix;
   private String lastName;
   private String phone1;
   private String phone2;
   private String EMail;
   private ArrayList roleValue;
   private ArrayList orderValue;

The beginning of the bean looks very much like its Customer Bean counterpart in Chapter 11, with the exception that it implements EntityBean. I won't show all the accessors for the attributes; they appear just as they do in the Chapter 11 version. The big difference with BMP is that the accessors aren't declared abstract public. Next we have the callback operations we are obligated to implement because we're dealing with an entity bean. We will focus on the ejbCreate() method:

public void ejbCreate(CustomerValue custVal) throws
   CreateException {
     customerInsert(custVal);
}

This method, which the UCMaintainRltnshp control class accesses via the matching create() stub in the CustomerBeanHome interface, invokes a local operation, customerInsert():

public void customerInsert(CustomerValue custVal)
    throws EJBExeption {

    try {
      setCustomerValue(custVal);
      DataAccess custDAO = new CustomerDAO();
      custDAO.insertObject(custVal);
      custDAO = null;
     } catch (DAODBUpdateException ae) {
       throw new EJBException (ae);
     } catch (DAOSysException se) {
       throw new EJBException (se);
     }
}

The customerInsert() operation is the same one as in Chapter 11—just slimmed down a bit. There is no longer a TransactionContext object being passed in or one being sent out with the creation of the CustomerDAO object, but we are working through the DataAccess interface just as before.

Let's now visit the CustomerDAO class, which has a new constructor:

public CustomerDAO() throws DAOSysException {
     InitialContext initCtx = null;

     try {
       initCtx = new InitialContext();
       DataSource ds = (javax.sql.DataSource)
         initCtx.lookup("java:comp/env/jdbc/remulak-bea");
       dbConnection = ds.getConnection();

     } catch(NamingException ne) {
       log("Failed to lookup JDBC Datasource. Please double
       check that");
       log("the JNDI name defined in the resource-description
       of the ");
       log("EJB's weblogic-ejb-jar.xml file is the same as the
       JNDI");
       log("name ");
       log("for the Datasource defined in your config.xml.");
       throw new DAOSysException(ne);

     } finally {
       try {
         if(initCtx != null) initCtx.close();
       } catch(NamingException ne) {
        log("Error closing context: " + ne);
        throw new DAOSysException(ne);
     }
   }
}

In the constructor we attain a reference to our JDBC data source and establish a connection. The lookup is done through JNDI, and this part of the application will also vary depending on the container product. The difference will be more syntax versus functionality. The lookup must happen regardless of the vendor. What follows is the insertObject() operation that the CustomerBean's ejbCreate() operation instigated:

public void insertObject(Object model) throws
            DAOSysException, DAODBUpdateException {

    CustomerValue custVal = (CustomerValue) model;

    PreparedStatement stmt = null;
    try {
      String queryStr = "INSERT INTO " + "T_Customer" + " (" +
        "customerId, " +
        "customerNumber, " +
        "firstName, " +
        "middleInitial, " +
        "prefix, " +
        "suffix, " +
        "lastName, " +
        "phone1, " +
        "phone2, " +
        "eMail) " +
        "VALUES " +
        "(?, ?, ?, ?, ?, ?, ?, ?, ?, ?)";

      stmt = dbConnection.prepareStatement(queryStr);

      int i = 1;
      stmt.setInt(i++, custVal.getCustomerId().intValue());
      stmt.setString(i++, custVal.getCustomerNumber());
      stmt.setString(i++, custVal.getFirstName());
      stmt.setString(i++, custVal.getMiddleInitial());
      stmt.setString(i++, custVal.getPrefix());
      stmt.setString(i++, custVal.getSuffix());
      stmt.setString(i++, custVal.getLastName());
      stmt.setString(i++, custVal.getPhone1());
      stmt.setString(i++, custVal.getPhone2());
      stmt.setString(i++, custVal.getEMail());

      int resultCount = stmt.executeUpdate();
      if ( resultCount != 1 )
        throw new DAODBUpdateException
         ("ERROR inserting Customer in" +
        " Customer_TABLE!! resultCount = " + resultCount);
   } catch(SQLException se) {
       throw new DAOSysException
        ("Unable to insert item " +
        custVal.getCustomerId() + " \n" + se);
    } finally {
      closeStatement(stmt);
      closeConnection();
    }
}

The logic is identical to the CustomerDAO version from Chapter 11. The only minor exception is that the reference to the Transaction Context object is gone and the connection itself is maintained locally in the dbConnection attribute, which was set in the constructor.

That completes our BMP preview. The complete source code is available (as described in preface of this book) to allow a full investigation of the differences. All the other operations in the bean follow the same pattern that we see with the insert.

  • + 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