A parent interface for all of the other interfaces in the business object layer.
Interface for the factory class used to create instances of business layer objects,
Interface for a utility object containing various methods used by
A parent interface for all of the other interfaces handling business processing.
Interface representing a single application request log entry stored in the
Interface for business logic methods having to do with request logs.
Interface representing a single application setting stored in the
Interface representing application settings stored in the database.
Interface representing an end user accessing the system.
Abstract superclass for all objects in the business layer.
Abstract superclass for all processing objects in the business layer.
Processes business logic having to do with request logs.
Factory class used to create instances of business layer objects.
A utility object containing various methods used by
An example of a class which may be run from the command line to execute processing within the system.
A class which may be run from the command line to check for orders whose payments were processed (through Authorize.net DPM) but where the order itself was not processed and marked complete in the system.
A class which may be run from the command line to reindex the Lucene index.
A class which may be run from the command line to sort products or categories.
An abstract useful for subclassing by classes that need to be invoked from the command line.
Static methods supporting "YYYY-MM-DD" dates.
Represents a single entry in the request log, ie, a single request made by a user to the application.
Record the sscRequestLog.requestLogID with each Envers revision.
Represents a single setting used by the application.
Represents various settings used by the application.
Represents an end user accessing the system.
Exception class for exceptions thrown by the application.
BusinessObject interface is extended by all other interfaces
in the business object layer, in much the same way
is subclassed by all the implementations in the business object layer. These
two entities provide a common set of methods business objects in the system
use to communicate with the rest of the application.
SettingsBean class is used to look up the various
settings stored in the system. And the
UserBean class represents
the properties of a given user in the system. It is used throughout the
application to store a given user's state.
Copyright © SoftSlate, LLC 20032012