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

Operation Context


Classes

struct  axis2_op_ctx_ops
 Message Context ops struct Encapsulator struct for ops of axis2_op_ctx. More...
struct  axis2_op_ctx
 Message Context struct Axis2 Message Context. More...

Defines

#define AXIS2_OP_CTX_GET_BASE(op_ctx, env)   ((op_ctx)->ops->get_base(op_ctx, env))
#define AXIS2_OP_CTX_FREE(op_ctx, env)   ((op_ctx)->ops->free(op_ctx, env))
#define AXIS2_OP_CTX_INIT(op_ctx, env, conf)   ((op_ctx)->ops->init(op_ctx, env, conf))
#define AXIS2_OP_CTX_GET_OP(op_ctx, env)   ((op_ctx)->ops->get_op(op_ctx, env))
#define AXIS2_OP_CTX_GET_PARENT(op_ctx, env)   ((op_ctx)->ops->get_parent(op_ctx, env))
#define AXIS2_OP_CTX_ADD_MSG_CTX(op_ctx, env, msg_ctx)   ((op_ctx)->ops->add_msg_ctx(op_ctx, env, msg_ctx))
#define AXIS2_OP_CTX_GET_MSG_CTX(op_ctx, env, message_id)   ((op_ctx)->ops->get_msg_ctx(op_ctx, env, message_id))
#define AXIS2_OP_CTX_GET_IS_COMPLETE(op_ctx, env)   ((op_ctx)->ops->get_is_complete(op_ctx, env))
#define AXIS2_OP_CTX_SET_IS_COMPLETE(op_ctx, env, is_complete)   ((op_ctx)->ops->set_complete(op_ctx, env, is_complete))
#define AXIS2_OP_CTX_CLEANUP(op_ctx, env)   ((op_ctx)->ops->cleanup(op_ctx, env))
#define AXIS2_OP_CTX_SET_PARENT(op_ctx, env, svc_ctx)   ((op_ctx)->ops->set_parent(op_ctx, env, svc_ctx))
#define AXIS2_OP_CTX_GET_MSG_CTX_MAP(op_ctx, env)   ((op_ctx)->ops->get_msg_ctx_map(op_ctx, env))

Typedefs

typedef axis2_op_ctx_ops axis2_op_ctx_ops_t
typedef axis2_op_ctx axis2_op_ctx_t

Functions

AXIS2_EXTERN axis2_op_ctx_taxis2_op_ctx_create (const axis2_env_t *env, struct axis2_op *op, struct axis2_svc_ctx *svc_ctx)

Detailed Description

An op context represents a running "instance" of an op, which is represented by an axis2_op struct. This concept is needed to allow messages to be grouped into ops as in WSDL 2.0-speak ops are essentially arbitrary message exchange patterns. So as messages are being exchanged the op context remembers the state of where in the message exchange pattern it is in. <p/> The base implementation of op context supports MEPs which have one input message and/or one output message. That is, it supports the all the MEPs that are in the WSDL 2.0 specification. In order to support another MEP one must extend this struct.
Generated on Fri Jun 16 18:02:46 2006 for Axis2/C by  doxygen 1.4.2