Package com.boylesoftware.cb2

The CB2 core, which includes the most fundamental services such as application context, business level and database access level implementations.

See:
Description

Interface Summary

AuthenticationListener	BLOs can implement this interface if they want to be notified about user logins and logouts.
BLOContainerStateListener	Interface, which can be implemented by BLOs if they want to be notified about changes in the BLO container's state, such as BLO container gets locked or unlocked.
BroadcastMessagingProvider	Interface for CB2 Broadcast Messaging provider implementations.
BroadcastMessagingTerminal	CB2 Broadcast Messaging clients (the BCM terminals) implement this interface and register within the application context under specific BCM channel names to receive broadcast messages.
DAOPlugin	Common parent interface for various DAO plugin subinterfaces.
FetchExecutor	Interface for modules that are used by the DAO's fetch calls to prepare and execute SQL statements.
FetchResultProcessor	Classes that implement this interface can be passed along with a DAO fetch call to be installed into the DAO's result set processing loop to perform certain operations on the DMs as they are coming out of the DAO and before they get packed into an array and returned back to the caller.
QueryParamProcessor	Interface for DAO plugins that perform additional processing of query parameters just before they get set into a prepared statement during a DAO call.
QueryParamSetter	Interface for the DAO plugin, which is responsible for setting query parameters into JDBC prepared statements during a DAO call.
ResultSetFieldGetter	Interface for the DAO plugin, which is responsible for getting column values from the result set during a DAO fetch call.
ResultSetFieldProcessor	Interface for DAO plugins that perform additional processing of data from result set columns just before they get set into DM fields during a DAO fetch call.
StatusProvider	Interface for objects that provide information about their internal status, environment, and operation statistics.
TransactionContext	Interface for transaction context implementations used by the application context to manage database transactions.

Class Summary

ApplicationContext	ApplicationContext class provides low-level application-wide services available to all application parts at all times.
BLErrors	Container for Business Level errors reported by a BLO.
BLManager	Business Level Manager singleton, which represents the Business Level of a CB2-based application.
BLObject	Parent abstract class for Business Level Objects (the BLOs), that are software components in the CB2 architecture that represent various business entities and implement application's business logic.
BLOContainer	As its name suggests, BLO container contains BLOs.
DAO	Database Access Object (the DAO) provides high-level API for database operations.
DAOConfig	DAO configuration built from a <dao-config> element in the blo-config.xml file.
DataModel	Parent class for Data Models used by the DAO.
DynamicDataModel	Special implementation of Data Model, which is not associated with any specific result set, but is able to contain any data in a form of name-value mappings.
FetchResultDescriptor	Descriptor or a result set processed by a DAO fetch call.
FetchResultProcessorHandler	Wrapper for FetchResultPocessor interface implementations, so they can be passed to the DAO along with a fetch call.
GenericFetchExecutor	Generic FetchExecutor implementation used by the DAO by default when no other DAO plugin implementing FetchExecutor interface is installed.

Exception Summary

ApplicationException	CB2 exception generated on the application context level.
BLException	Indicates an unexpected failure in the Business Level.
NoBLOContainerException	Indicates that there is no BLO container instance for the requested session.
TooManyWaitingThreadsException	Thown by the BL Manager's getBLOContainer method to indicate that there are already too many threads waiting for the BLO container to get unlocked.

Package com.boylesoftware.cb2 Description

The CB2 core, which includes the most fundamental services such as application context, business level and database access level implementations.

A CB2-based application usually maintains two application-wide singletons that represent the Application Context and the Business Level Manager. All other services are accessed through these two basic objects. For example, a simple console application could have the following in its main method:

public static void main(String [] args)
    throws Exception {

    ApplicationContext appCtx = null;
    BLManager blManager = null;
    try {
        appCtx = new ApplicationContext("myApp", "");
        blManager = new BLManager(appCtx);

        ...

    } finally {
        if(blManager != null)
            blManager.destroy();
        if(appCtx != null)
            appCtx.destroy();
    }
}

Note that if your application is using some Presentation Level framework, such as the Apache Struts based PL framework that comes with CB2 library (see com.boylesoftware.cb2.presentation.servlet package), you don't have to worry about creating, maintaining and destroying Application Context and BL Manager objects - the framework does it for your application.