Rakesh API

Package biz.wedoit4u.ejb.session

This package contains Session Beans developed for the wedoit4u.biz site.

See:
          Description

Interface Summary
DatabaseAction This stateless session bean provides methods that deal with adding or modifying data in the wedoit4u database.
DatabaseActionHome The local home interface to the stateless session bean that implements the business logic for creating/modifying data in the wedoit4u schema tables.
DateFormatter This stateless session bean provides utility methods to convert dates into commonly needed string formats, as well as strings in commonly used date formats into Java Dates.
DateFormatterHome The local home interface to the stateless session bean that provides utility methods to convert dates into commonly needed string formats, as well as strings in commonly used date formats into Java Dates.
 

Class Summary
DatabaseActionBean The implementation of the DatabaseAction session bean.
DateFormatterBean Common date transformations that are performed.
SessionBeanAdapter An adapter class that provides empty implementation for all the methods specified in the SessionBean interface.
SessionBeanProvider This class provides utility methods to access the Session Beans that are available in this package.
 

Package biz.wedoit4u.ejb.session Description

This package contains Session Beans developed for the wedoit4u.biz site.

The Session Beans developed are mostly Stateless, and are used primarily for routine tasks that need to be executed by the classes that were developed for wedoit4u.biz site.

Naming Convention

The following list describes the conventions for each component of a session bean:

  1. Interface: This interface is not necessary for EJB's, but are used for all session and entity beans developed to help do basic implementation compliance checking by the Java compiler prior to deployment on the application server. All interfaces are named as:

    <Session Bean Remote Interface Name>Interface


    For instance the interface for the DateFormatter session bean is named DateFormatterInterface.
  2. Remote Interface: The remote interface provides access to the business methods supported by the EJB module. The remote interfaces are given names that appropriately describe their function. For instance the session bean that provides standard date parsing/formatting methods is named DateFormatter.
  3. Home Interface: The home interface for session beans are used to create and destroy instances of the remote interface by clients. Home interfaces are always named as:

    <Session Bean Remote Interface Name>Home


    For instance the home interface to the DateFormatter session bean is named DateFormatterHome.
  4. Bean Implementation: The EJB class that implements the business logic necessary for the EJB module is named as:

    <Session Bean Remote Interface Name>Bean.


    For instance the bean implementation of the DateFormatter session bean is named DateFormatterBean.

For ease of use, a convenience class SessionBeanProvider is provided, that encapsulates access to the session bean instances. This helps keep client code independant of the JNDI locations for the beans.


Rakesh API

Copyright © 2002-2005 - Rakesh Vidyadharan