All Classes and Interfaces
Class
Description
Application framework logging for the ccee-library.
The log by default checks for the availability of the normal CaptainCasa log which is part of the CaptainCasa server library (eclnt_jsfserver.jar).
The log by default checks for the availability of the normal CaptainCasa log which is part of the CaptainCasa server library (eclnt_jsfserver.jar).
Facade for accessing logic behind scheduler.
Utility for deeply cloning objects by serializing and de-serializing.
Central class for getting configuration parameters.
Creation of Java-code for a facade class.
Class for accessing the database - i.e. for building up the connection to the
database.
This class is in general not directly used by the application processing.
This class is in general not directly used by the application processing.
Data structure that is passed back when picking a connection.
Environment for executing (transactional) operations against database.
Executes a SQL script for creating database artifacts (tables, views, ...).
Special variant of
DBAction.Java API to access Deepl free translation services in a simple way.
Default implementation that can be used in order to extend your own
implementation.
Class that configures the web application context in case of using
annotations.
Spring Annotation based context that is aware of HotDeployment classloader.
Spring Annotation based context that is aware of HotDeployment classloader.
CaptainCasa' server processing is always within a scope of a dialog session.
CaptainCasa' server processing is always within a scope of a dialog session.
CaptainCasa' server processing is always within a scope of a dialog session.
Spring XML based context that is aware of HotDeployment classloader.
Spring XML based context that is aware of HotDeployment classloader.
CaptainCasa' server processing is always within a scope of a dialog session.
Dispatcher that uses Spring context to access page beans.
Dispatcher that uses Spring context to access page beans.
Dispatcher that uses Spring context to access page beans.
Central management of DB syntax differences during automated creation
of SQL statements.
Entity meta data.
Execution processing to the database.
Complex definition of an SQL function.
Dummy implementation of IDynDataLiteralResolver.
Utility to transform a DynData-instance into meta data.
Instance of dynamic data.
Context information that is passed into the resolution of dynamic data.
Generic client side facade processing on client side.
Wrapper for facade exceptions on client caller side.
Server side caller of facade - taking the serialized call-information,
calling the facade and transferring the result information into
a serialized result.
Wrapper of exception that may have occurred on server side.
Direct calling of
FacadeServer in the same class loader.Transfer of content via simple http-post.
Serialized data for passing back the result.
Serialized data for passing back the facade call.
Utitlity functions around accessing other systems by http
Utility functions in the area of Java-http processing.
Check if this node is active for serving as scheduler node.
Central constants to be used within the CCEE framework.
Interface to provide configuration values that are kept accessed via
Config.If running DOFW* functions inside some other DB framework then the database
connection might be passed by being attached to the current thread.
If the connection is created by using the configuration parameters
(i.e. not using
IDBConnectionProvider), then by default
the password of the connection is read from configuration parameter
"db_password". - Problem: the password of the connection needs to
be stored in a configuration file, which might be some security
risk.Interface to program checking the connection when it is picked from the pool.
Extension to interface
IDBConnectionProvider with addtional method
to pass back the parameter "db_autotrim"Literal resolution that is invoked by expression "#{literal(...)}" in the
processing of
DynDataMap.Transfer of facade method call data to the instance where the
facade actually is running - and transfer of parameters back.
Utility for comparing two images.
Extended functions for simple data type mapping - so that own simple data
types can be directly bound to data base operations.
Interface to update the table name that is sent to the query just before the query is transferred
into a prepared statement.
Interface for following single object manipulations inside
DOFWSql.Peristence interface that is used for storing variants.
Bridge to JSR380 javax.validation.
Bridge between
IClusterMessageQueue processing and actual IMessageQueue processing.Purpose: when using final variables then the instance itself
must not change.
Utility for managing "Pojos" - i.e. properties only consisting out of
data members and correspdoning setter/getter methods.
Create QRCode - using library com.google.zxing
Central class for scheduling.
Utitlity functions in the area of serializing objects to bytes.
Central registration of Spring Application Context.
Example implementation of
ITrace - printing log information to the console.Access to
ITrace implementation.Object that manages runtime configuration data for an object of instance
Example:
IExtractApply.Example:
IExtractApply is implemented for a grid, so that runtime
configuration of a user (e.g. sequence of columns) can be configured.Collection of information during validation.
Object which needs to be passed with
ICCEEConstants#BETTWEEN.Object which needs to be passed with
ICCEEConstants.IN.Factory access to
IVariantPersistence.Implementation of
IVariantPersistence that uses the
IStreamStore persistence.Caches objects of specific classes for a bean.