Home > Articles > Programming > Java

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

This chapter is from the book

In Practice

The ChalkTalk application needs the capability to read and save data to the database structure. We have read and written data to the database using JDBC; now it is time to accomplish the same task using entity beans. The process of building the beans is rather simple; most of our work will be executed in the session facade.

Building the Persistence Layer

The creation of the persistence layer using JBuilder depends on the appropriate data structure being completed. In Chapter 15, "Database Connectivity," we created the necessary data store for our application. We will now create the entity beans to manage this persistence. The following steps are used to build the necessary entity beans:The creation of the persistence layer using JBuilder depends on the appropriate data structure being completed. In Chapter 15, "Database Connectivity," we created the necessary data store for our application. We will now create the entity beans to manage this persistence. The following steps are used to build the necessary entity beans:

  1. Import a schema from our data source in the EJB module containing our session beans. This is accomplished by right-clicking on the data source node when we are in the EJB Designer and selecting Import Schema from Datasource.

  2. Set the following database parameters:

    • Driver: com.borland.datastore.jdbc.DataStoreDriver

    • URL: jdbc:borland:dslocal:C:\JBDG\db\ChalkTalk.jds

    • Username: leave blank

    • Password: leave blank

  3. Right-click on each table and create a CMP 2.0 entity bean for each table. For example, right click on the table Room and create a CMP 2.0 bean.

  4. Define relationships.

Configuring an Entity Bean

Typically each entity bean that has been created requires more finder methods than just a findByPrimaryKey. Our Room entity bean is a perfect example.

  1. Right-click on our Room entity bean. Add a finder method.

  2. Configure the following properties for the finder method:

    • Name: findAll

    • Return type: java.util.Collection

    • Input parameters: leave empty

    • Home interfaces: Local Home

    • Query: SELECT OBJECT(o) FROM RoomSchema AS o

  3. Compile and save.

Creating an EJB Connection Factory

This factory supplies caching to both local and remote interfaces. Although this connection factory differentiates between local and remote interfaces, you have the capability to make this interface ubiquitous. The following steps build your EJB connection factory:

  1. Create a new class within your project, calling it EJBConnectionFactory.

  2. Move the newly created class to the package com.sams.chalktalk.beans.

  3. Add the following code to implement the connection to both local and remote beans in addition to placing them into a cache when the connection has been established:

  4. package com.sams.chalktalk.beans;
    
    import javax.naming.*;
    import java.util.*;
    import javax.ejb.*;
    
    class EJBHomeFactory {
    
     private static EJBHomeFactory instance = null;
     private Context initialContext;
     private Map ejbHomes;
    
     private EJBHomeFactory() throws NamingException {
      initialContext = new InitialContext();
      ejbHomes = Collections.synchronizedMap(new HashMap());
     }
    
     public static EJBHomeFactory getInstance() throws NamingException {
      if(instance == null) {
       instance = new EJBHomeFactory();
      }
      return instance;
     }
    
     public EJBLocalHome lookupByLocalEJBReference(String ejbReferenceComponent)
      throws NamingException {
    
      java.lang.Object home = ejbHomes.get(ejbReferenceComponent);
      if(home == null) {
       home = initialContext.lookup("java:comp/env/ejb/" + 
                      ejbReferenceComponent);
       ejbHomes.put(ejbReferenceComponent, home);
      }
      return (EJBLocalHome) home;
     }
    
     public EJBHome lookupByRemoteEJBReference(String ejbReferenceComponent, 
       Class homeClass)
      throws NamingException {
    
      java.lang.Object home = ejbHomes.get(ejbReferenceComponent);
      if(home == null) {
       java.lang.Object obj =
        initialContext.lookup("java:comp/env/ejb/" + ejbReferenceComponent);
       home = javax.rmi.PortableRemoteObject.narrow(obj, homeClass);
       ejbHomes.put(ejbReferenceComponent, home);
      }
      return (EJBHome) home;
     }
    }
  5. Compile and save your project.

Creating a Manager Bean

A manager bean surfaces the business logic and ultimately interfaces to the persistence utilizing the entity beans. These manager beans will then be attached to the session facade to consolidate the middle-tier access. The following steps are required to create one of the manager beans:

  1. Create a new class, naming the class RoomManager and placing the new class in the package com.sams.chalktalk.beans.

  2. The following code surfaces the required business logic. The requirements of the manager class are used to implement all the appropriate business logic, such as checking to make sure that a room has a capacity.

  3. package com.sams.chalktalk.beans;
    
    import javax.naming.*;
    import javax.ejb.*;
    import java.util.*;
    
    class RoomManager {
     //Add a home factory for caching the home interfaces
     private EJBHomeFactory homeFactory;
     private static RoomManager instance = null;
     
     //Use the RoomValueFactory to create
     private RoomValueFactory roomValueFactory;
    
     private RoomManager() throws NamingException {
      homeFactory = EJBHomeFactory.getInstance();
     }
    
     public static RoomManager getInstance() throws NamingException {
      if(instance == null) {
       instance = new RoomManager();
      }
      return instance;
     }
    
     public String createRoom(RoomValue roomValue)
       throws FinderException, NamingException {
    
      try {
       RoomHome roomHome =
         (RoomHome) homeFactory.lookupByLocalEJBReference("Room");
       Room room = roomHome.create(roomValue.getLocation(),roomValue. getCapacity()
    ,roomValue.getName(),roomValue.getKey());
       return room.getName();
      }
      catch(Exception e) {
       throw new EJBException(e);
      }
     }
    
     public void updateRoom(RoomValue roomValue)
       throws FinderException, NamingException {
    
      try {
       Room room = roomValueFactory.findRoom(roomValue.getKey());
       room.setCapacity(roomValue.getCapacity());
      }
      catch(Exception e) {
       throw new EJBException(e);
      }
     }
    
     public void removeRoom(Short key)
       throws FinderException, NamingException {
    
      try {
       Room room = roomValueFactory.findRoom(key);
       room.remove();
      }
      catch(Exception e) {
       throw new EJBException(e);
      }
     }
    
     public void removeAllRooms()
       throws FinderException, NamingException {
    
      try {
       Collection rooms = roomValueFactory.findAllRooms();
       Iterator iterator = rooms.iterator();
       Room room = null;
       while(iterator.hasNext()) {
        room = (Room) iterator.next();
        room.remove();
       }
      }
      catch(Exception e) {
       throw new EJBException(e);
      }
     }
    }

Attaching the Session Facade

Our session facade wraps multiple manager beans together into one session bean. In other words, we will access all functionality for our ChalkTalk system utilizing this one session bean. The following steps are required to attach the facade to our manager bean:

  1. Define a private member for each type of bean manager you want to use. For example, the following code defines one for our RoomManager:

  2.  private RoomManager roomManager;
  3. Create an instance of our manager bean within ejbCreate(). The following demonstrates the implementation using our RoomManager:

  4.  public void ejbCreate() throws CreateException {
      try {
       roomManager = RoomManager.getInstance();
      }
      catch (NamingException ex) {
       //pass exception to the container
       throw new EJBException(ex);
      }
  5. Attach the manager bean call to be called from the corresponding session bean method. If the client calls the createRoom method of the session bean, it then needs to pass the information to the manager class. The following code demonstrates such an implementation:

  6.  public void createRoom(RoomValue room) {
      try {
       roomManager.createRoom(room);
      }
      catch (Exception ex) {
        throw new EJBException(ex);
      }
     }
  7. Compile and save your project.

Testing the Implementation

It is time to test the client we created. The easiest way to test the session facade is to build a client dedicated to testing the interface. The following steps build a test client to exercise this facade:

  1. Select File, New from the JBuilder menu.

  2. Within the Object Gallery, under the Enterprise tab, select the EJB Test Client.

  3. Specify the following parameters to build our test client:

    • EJB name: ChalkTalkFacade

    • Package: com.sams.chalktalk.client

    • Class name: ChalkTalkFacadeTestClient

    • Generate Method for Testing Remote Interface Calls with Arguments: Checked

    • Generate Logging Messages: Checked

    • Generate Main Functions: Checked

    • Generate Header Comments: Checked

  4. Add the following code to the main method to test your session bean interface:

  5.   //create a Remote interface
      client.create();
    
      //Add a room
      client.addRoom(new RoomData(5,"Small Room",5,"2nd Floor"));
    
      //Add with invalid capacity
      client.addRoom(new RoomData(3,"Error Room",0,"3rd Floor"));
  6. Save, compile, and run your test application.

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