Issues in the Axis2/C Manual - Writing a Module
-----------------------------------------------
Key: AXIS2C-576
URL: https://issues.apache.org/jira/browse/AXIS2C-576
Project: Axis2-C
Issue Type: Bug
Components: documentation
Environment: Windows XP
Reporter: Evanthika Amarasiri
The following issues were found in the AxisC Manual (under the heading "Writing
a Module")
1. The code segments given below are different to what is actually given in the
sample logging module
**********************************************************************************
1.
axis2_status_t (AXIS2_CALL * init ) (axis2_module_t *module, const
axis2_env_t *env , axis2_conf_ctx_t *conf_ctx , axis2_module_desc_t
*module_desc)
The module initialisation is done here.
2.
axis2_status_t (AXIS2_CALL * shut_down ) (axis2_module_t *module, const
axis2_env_t *env )
Handler created function are stored in a hash map. This function will
remove them from the hash map.
3.
axis2_status_t (AXIS2_CALL *fill_handler_create_func_map )
(axis2_module_t *module, const axis2_env_t *env )
**********************************************************************************
Please update the manual with the latest code
2. What does it mean by "axis2_modules_ops" in the sentence "Every module
should have three basic functions as defined in the axis2_modules_ops." This is
not quite clear to me. Maybe a person familiar with these things might know
what it means but can we please change it into something which anyone would
understand?
3. The code segment given in the document is different to what is actually
given in the "log_in_handler.c" file.
*********************************************************************************
soap_envelope = AXIS2_MSG_CTX_GET_SOAP_ENVELOPE(msg_ctx, env);
if(soap_envelope)
{
AXIOM_SOAP_ENVELOPE_GET_BODY(soap_envelope, env);
ret_node = AXIOM_SOAP_ENVELOPE_GET_BASE_NODE(soap_envelope, env);
*********************************************************************************
In the above code segment, some of the variables are given in caps. In the
class file they are given in simple. Is this correct? Shouldn't the code
segment be replaced with what is given in the samples? Please update the manual
with the latest code.
4. The steps on how to write the module's in handlers, out handlers and the
module.xml are given but after that what should you do to make the module
usable. Is this enough? Can I just take this module folder and drop it inside
the "modules" folder which is inside "deploy"? Seems that more steps are needed
here as to how we can compile these files until you drop it inside the
AXIS2C_HOME/build/deply/modules folder.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
