Main Page | Modules | Class List | Directories | File List | Class Members | File Members | Examples

axis2_module.h File Reference

axis2 module interface Every module provides an implementation of this class. Modules are in one of three states: "available" and "initialized". All modules that the runtime detects (from the system modules/ directory or from other means) are said to be in the "available" state. If some service indicates a dependency on this module then the module is initialized (once for the life of the system) and the state changes to "initialized". <p/> <p/>Any module which is in the "initialized" state can be engaged as needed by the engine to respond to a message. Currently module engagement is done via deployment (using module.xml). In the future we may engage modules programmatically by introducing an engage() method to this interface, thereby allowing more dynamic scenarios. More...

#include <axis2_const.h>
#include <axis2_error.h>
#include <axis2_defines.h>
#include <axis2_env.h>
#include <axis2_allocator.h>
#include <axis2_string.h>
#include <axis2_conf.h>
#include <axis2_hash.h>

Go to the source code of this file.

Defines

#define AXIS2_MODULE_INIT(module, env)   ((module)->ops->init (module, env))
#define AXIS2_MODULE_SHUTDOWN(module, env)   ((module)->ops->shutdown (module, env))
#define AXIS2_MODULE_FILL_HANDLER_CREATE_FUNC_MAP(module, env)   ((module)->ops->fill_handler_create_func_map (module, env))

Typedefs

typedef axis2_module_ops axis2_module_ops_t
typedef axis2_module axis2_module_t

Functions

AXIS2_EXTERN axis2_module_t * axis2_module_create (const axis2_env_t *env)


Detailed Description

axis2 module interface Every module provides an implementation of this class. Modules are in one of three states: "available" and "initialized". All modules that the runtime detects (from the system modules/ directory or from other means) are said to be in the "available" state. If some service indicates a dependency on this module then the module is initialized (once for the life of the system) and the state changes to "initialized". <p/> <p/>Any module which is in the "initialized" state can be engaged as needed by the engine to respond to a message. Currently module engagement is done via deployment (using module.xml). In the future we may engage modules programmatically by introducing an engage() method to this interface, thereby allowing more dynamic scenarios.


Generated on Fri Jun 16 18:02:33 2006 for Axis2/C by  doxygen 1.4.2