Overview | Package | Class | Use | Tree | Deprecated | Index | Help
PREV NEXT | FRAMES NO FRAMES

## Uses of Package
org.makumba

Packages that use org.makumba
org.makumba | Public API for makumba application programmers.
org.makumba.analyser |
org.makumba.commons |
org.makumba.commons.attributes |
org.makumba.commons.formatters |
org.makumba.commons.tags |
org.makumba.controller |
org.makumba.db |
org.makumba.db.hibernate |
org.makumba.db.makumba |
org.makumba.db.makumba.sql | The generic SQL-92 implementation of the makumba database layer.
org.makumba.devel | the makumba developer support, such as MDD, JSP and Java viewers.
org.makumba.forms.html |
org.makumba.forms.responder |
org.makumba.forms.tags |
org.makumba.forms.validation |
org.makumba.importer |
org.makumba.list |
org.makumba.list.engine |
org.makumba.list.engine.valuecomputer |
org.makumba.list.html |
org.makumba.list.tags | Implements the JSP Tag Library to use makumba in JSP pages.
org.makumba.providers |
org.makumba.providers.datadefinition.makumba | Handles abstract part of makumba (data type handling and MDD parsing).
org.makumba.providers.datadefinition.makumba.validation |
org.makumba.providers.query.hql |
org.makumba.providers.query.mql |
org.makumba.providers.query.oql |
test | Contains automated tests for various makumba components.

Classes in org.makumba used by org.makumba
CompositeValidationException This class holds several `InvalidValueException` of the same form together.
Database Deprecated. Should use org.makumba.Transaction instead This class models operations with a database. To obtain such an object, use methods from `MakumbaSystem`. Stricly speaking this class represents a database connection (later on, transaction). Obtaining more such objects for the same database configurations will result in opening more connections. Connections must be given back to the system using the `Database.close()` method. That will be done automatically by the object's finalizer. In makumba business logic, connections passed to the BL methods are automatically closed by the system after the BL operations (including eventual automatic DB acceses) were completed. To open a "sibling" of a connection conn of this type, use MakumbaSystem.getConnectionTo(conn.getName()). In most cases, you will have to close the sibling yourself. At the level of this API, data is represented as java.util.Dictionary, both for reading and writing. Most methods throw `DBError` if a fatal database error occurs. If the connection to the database is lost, an attempt is made to reconnect before throwing a `DBError`. All methods throw subclasses of either Error or RuntimeException, so nothing needs to be caught explicitely.
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
DataDefinition.MultipleUniqueKeyDefinition Data structure holding the definition of a mult-field unique key.
DataDefinition.QueryFragmentFunction
DataDefinitionParseError Error occured during data definition parsing.
DBError A database error
DefinitionParseError This class provides basic support for definition parse errors.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.
HtmlUtils This class provides basic 'text-to-HTML' functionality.
InvalidValueException This exception occurs when an invalid value is passed to a field
LogicException An exception thrown during the execution of some business logic code
MakumbaError A generic Makumba fatal error, due to misconfiguration, bad Data Definition (MDD) syntax, bad OQL syntax, database fatal error, etc.
Pointer This class represents an abstract makumba pointer.
Text A makumba text, a byte array that can be converted to String when needed.
Transaction This class models operations with a database.
UnauthorizedException An unauthorized exception, due to mismatch of attribute values
ValidationDefinition Information about a makumba validation definition.
ValidationRule Defines the basics of a Makumba Validation rule.

Classes in org.makumba used by org.makumba.analyser
LogicException An exception thrown during the execution of some business logic code
ProgrammerError this error is thrown when a handler method is missing but it is needed by some controller

Classes in org.makumba used by org.makumba.commons
Attributes The attributes provided by a makumba environment (for example a http session).
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
Pointer This class represents an abstract makumba pointer.
Transaction This class models operations with a database.

Classes in org.makumba used by org.makumba.commons.attributes
Attributes The attributes provided by a makumba environment (for example a http session).
LogicException An exception thrown during the execution of some business logic code

Classes in org.makumba used by org.makumba.commons.formatters
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
InvalidValueException This exception occurs when an invalid value is passed to a field

Classes in org.makumba used by org.makumba.commons.tags
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.

Classes in org.makumba used by org.makumba.controller
Attributes The attributes provided by a makumba environment (for example a http session).
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
LogicException An exception thrown during the execution of some business logic code
LogicInvocationError This error occurs when an undesired business logic exception comes up.
Pointer This class represents an abstract makumba pointer.

Classes in org.makumba used by org.makumba.db
Attributes The attributes provided by a makumba environment (for example a http session).
Database Deprecated. Should use org.makumba.Transaction instead This class models operations with a database. To obtain such an object, use methods from `MakumbaSystem`. Stricly speaking this class represents a database connection (later on, transaction). Obtaining more such objects for the same database configurations will result in opening more connections. Connections must be given back to the system using the `Database.close()` method. That will be done automatically by the object's finalizer. In makumba business logic, connections passed to the BL methods are automatically closed by the system after the BL operations (including eventual automatic DB acceses) were completed. To open a "sibling" of a connection conn of this type, use MakumbaSystem.getConnectionTo(conn.getName()). In most cases, you will have to close the sibling yourself. At the level of this API, data is represented as java.util.Dictionary, both for reading and writing. Most methods throw `DBError` if a fatal database error occurs. If the connection to the database is lost, an attempt is made to reconnect before throwing a `DBError`. All methods throw subclasses of either Error or RuntimeException, so nothing needs to be caught explicitely.
Pointer This class represents an abstract makumba pointer.
ProgrammerError this error is thrown when a handler method is missing but it is needed by some controller
Transaction This class models operations with a database.

Classes in org.makumba used by org.makumba.db.hibernate
Attributes The attributes provided by a makumba environment (for example a http session).
Database Deprecated. Should use org.makumba.Transaction instead This class models operations with a database. To obtain such an object, use methods from `MakumbaSystem`. Stricly speaking this class represents a database connection (later on, transaction). Obtaining more such objects for the same database configurations will result in opening more connections. Connections must be given back to the system using the `Database.close()` method. That will be done automatically by the object's finalizer. In makumba business logic, connections passed to the BL methods are automatically closed by the system after the BL operations (including eventual automatic DB acceses) were completed. To open a "sibling" of a connection conn of this type, use MakumbaSystem.getConnectionTo(conn.getName()). In most cases, you will have to close the sibling yourself. At the level of this API, data is represented as java.util.Dictionary, both for reading and writing. Most methods throw `DBError` if a fatal database error occurs. If the connection to the database is lost, an attempt is made to reconnect before throwing a `DBError`. All methods throw subclasses of either Error or RuntimeException, so nothing needs to be caught explicitely.
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.
LogicException An exception thrown during the execution of some business logic code
Pointer This class represents an abstract makumba pointer.
Text A makumba text, a byte array that can be converted to String when needed.
Transaction This class models operations with a database.

Classes in org.makumba used by org.makumba.db.makumba
Attributes The attributes provided by a makumba environment (for example a http session).
Database Deprecated. Should use org.makumba.Transaction instead This class models operations with a database. To obtain such an object, use methods from `MakumbaSystem`. Stricly speaking this class represents a database connection (later on, transaction). Obtaining more such objects for the same database configurations will result in opening more connections. Connections must be given back to the system using the `Database.close()` method. That will be done automatically by the object's finalizer. In makumba business logic, connections passed to the BL methods are automatically closed by the system after the BL operations (including eventual automatic DB acceses) were completed. To open a "sibling" of a connection conn of this type, use MakumbaSystem.getConnectionTo(conn.getName()). In most cases, you will have to close the sibling yourself. At the level of this API, data is represented as java.util.Dictionary, both for reading and writing. Most methods throw `DBError` if a fatal database error occurs. If the connection to the database is lost, an attempt is made to reconnect before throwing a `DBError`. All methods throw subclasses of either Error or RuntimeException, so nothing needs to be caught explicitely.
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
DataTransformer Specifies interface for data transformation.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.
LogicException An exception thrown during the execution of some business logic code
Pointer This class represents an abstract makumba pointer.
Transaction This class models operations with a database.

Classes in org.makumba used by org.makumba.db.makumba.sql
CompositeValidationException This class holds several `InvalidValueException` of the same form together.
Database Deprecated. Should use org.makumba.Transaction instead This class models operations with a database. To obtain such an object, use methods from `MakumbaSystem`. Stricly speaking this class represents a database connection (later on, transaction). Obtaining more such objects for the same database configurations will result in opening more connections. Connections must be given back to the system using the `Database.close()` method. That will be done automatically by the object's finalizer. In makumba business logic, connections passed to the BL methods are automatically closed by the system after the BL operations (including eventual automatic DB acceses) were completed. To open a "sibling" of a connection conn of this type, use MakumbaSystem.getConnectionTo(conn.getName()). In most cases, you will have to close the sibling yourself. At the level of this API, data is represented as java.util.Dictionary, both for reading and writing. Most methods throw `DBError` if a fatal database error occurs. If the connection to the database is lost, an attempt is made to reconnect before throwing a `DBError`. All methods throw subclasses of either Error or RuntimeException, so nothing needs to be caught explicitely.
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
DataDefinition.MultipleUniqueKeyDefinition Data structure holding the definition of a mult-field unique key.
DBError A database error
Pointer This class represents an abstract makumba pointer.
Transaction This class models operations with a database.

Classes in org.makumba used by org.makumba.devel
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.
MakumbaError A generic Makumba fatal error, due to misconfiguration, bad Data Definition (MDD) syntax, bad OQL syntax, database fatal error, etc.
Pointer This class represents an abstract makumba pointer.

Classes in org.makumba used by org.makumba.forms.html
CompositeValidationException This class holds several `InvalidValueException` of the same form together.
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
InvalidValueException This exception occurs when an invalid value is passed to a field

Classes in org.makumba used by org.makumba.forms.responder
CompositeValidationException This class holds several `InvalidValueException` of the same form together.
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.
InvalidValueException This exception occurs when an invalid value is passed to a field
LogicException An exception thrown during the execution of some business logic code
Pointer This class represents an abstract makumba pointer.

Classes in org.makumba used by org.makumba.forms.tags
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.
LogicException An exception thrown during the execution of some business logic code

Classes in org.makumba used by org.makumba.forms.validation
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.

Classes in org.makumba used by org.makumba.importer
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
MakumbaError A generic Makumba fatal error, due to misconfiguration, bad Data Definition (MDD) syntax, bad OQL syntax, database fatal error, etc.
Pointer This class represents an abstract makumba pointer.
Transaction This class models operations with a database.

Classes in org.makumba used by org.makumba.list
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.
LogicException An exception thrown during the execution of some business logic code

Classes in org.makumba used by org.makumba.list.engine
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
LogicException An exception thrown during the execution of some business logic code

Classes in org.makumba used by org.makumba.list.engine.valuecomputer
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.
LogicException An exception thrown during the execution of some business logic code

Classes in org.makumba used by org.makumba.list.html
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.

Classes in org.makumba used by org.makumba.list.tags
LogicException An exception thrown during the execution of some business logic code

Classes in org.makumba used by org.makumba.providers
Attributes The attributes provided by a makumba environment (for example a http session).
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
DataDefinitionParseError Error occured during data definition parsing.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.
LogicException An exception thrown during the execution of some business logic code
Pointer This class represents an abstract makumba pointer.
Transaction This class models operations with a database.

Classes in org.makumba used by org.makumba.providers.datadefinition.makumba
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
DataDefinition.MultipleUniqueKeyDefinition Data structure holding the definition of a mult-field unique key.
DataDefinition.QueryFragmentFunction
DataDefinitionParseError Error occured during data definition parsing.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.
ValidationDefinition Information about a makumba validation definition.
ValidationDefinitionParseError Error occured during validation definition parsing.
ValidationRule Defines the basics of a Makumba Validation rule.

Classes in org.makumba used by org.makumba.providers.datadefinition.makumba.validation
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.
InvalidValueException This exception occurs when an invalid value is passed to a field
ValidationDefinitionParseError Error occured during validation definition parsing.
ValidationRule Defines the basics of a Makumba Validation rule.

Classes in org.makumba used by org.makumba.providers.query.hql
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.

Classes in org.makumba used by org.makumba.providers.query.mql
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.

Classes in org.makumba used by org.makumba.providers.query.oql
DataDefinition Information about a makumba data definition as obtained from an MDD file or the structure of an OQL query result.
FieldDefinition Information about a field from a makumba data definition as obtained from an MDD file.

Classes in org.makumba used by test
Attributes The attributes provided by a makumba environment (for example a http session).
Database Deprecated. Should use org.makumba.Transaction instead This class models operations with a database. To obtain such an object, use methods from `MakumbaSystem`. Stricly speaking this class represents a database connection (later on, transaction). Obtaining more such objects for the same database configurations will result in opening more connections. Connections must be given back to the system using the `Database.close()` method. That will be done automatically by the object's finalizer. In makumba business logic, connections passed to the BL methods are automatically closed by the system after the BL operations (including eventual automatic DB acceses) were completed. To open a "sibling" of a connection conn of this type, use MakumbaSystem.getConnectionTo(conn.getName()). In most cases, you will have to close the sibling yourself. At the level of this API, data is represented as java.util.Dictionary, both for reading and writing. Most methods throw `DBError` if a fatal database error occurs. If the connection to the database is lost, an attempt is made to reconnect before throwing a `DBError`. All methods throw subclasses of either Error or RuntimeException, so nothing needs to be caught explicitely.
LogicException An exception thrown during the execution of some business logic code
Pointer This class represents an abstract makumba pointer.
Transaction This class models operations with a database.

Overview | Package | Class | Use | Tree | Deprecated | Index | Help
PREV NEXT | FRAMES NO FRAMES

Docs generated on 2009-02-25 14:20