[
https://issues.apache.org/jira/browse/AXIS2C-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Samisa Abeysinghe resolved AXIS2C-569.
--------------------------------------
Resolution: Fixed
Fixed the API issues and the spelling issues.
Many thanks for the detailed review.
> Issues in the Axis2/C Manual - Service API and some typos found of the entire
> guide
> -----------------------------------------------------------------------------------
>
> Key: AXIS2C-569
> URL: https://issues.apache.org/jira/browse/AXIS2C-569
> Project: Axis2-C
> Issue Type: Bug
> Components: documentation
> Affects Versions: Current (Nightly)
> Environment: Windows XP
> Reporter: Evanthika Amarasiri
> Assigned To: Samisa Abeysinghe
> Fix For: 1.0.0
>
>
> The below issues were found in the Axis2/C Manual - Quick Start Guide and
> some typo errors were found as well (of the whole document )
> 1. In the code segment which is given, a ")" is missing in the math_free
> function
> E.g.:- math_free (axis2_svc_skeleton_t *svc_skeleton, const axis2_env_t *env
> - The close bracket is missing
> 2. The code segment given in the manual is different from what is actually
> given in the sample. Please update the manual with the correct code
> E.g.:- method "math_free"
> a) Given in the manual - AXIS2_FREE(env->allocator, svc_skeleton ->ops);
> Given in the sample - AXIS2_FREE(env->allocator, svc_skeleton);
> b) Given in the manual - svc_skeleton -> NULL;
> Given in the sample - svc_skeleton = NULL;
> c) method "math_invoke"
> In the code segment which is given in the manual lacks four closing brackets
> "}". Replace this with the correct code as well
> Similarly the rest of the code segments given in the manual should match with
> what is actually given in the samples.
> 3. The following typos should be corrected
> a) Under "4. Client API > Two-way or One-way transport", "seperate chanel"
> should be corrected as "separate channel"
> b) Under "4. Client API > Two-way or One-way transport", the word of the
> sentence "If we want to use a seperate channel" the word "seperate" should be
> corrected as "separate"
> c) Under "4. Client API > Two-way or One-way transport", the word "ApendixD"
> should be corrected as "Appendix D"
> d) Under "4. Client API > Synchronous/Asynchronous Behaviour
> (Blocking/Non-Blocking)" the word "Sysnchronous" should be corrected as
> "Synchronous"
> e) Under "5. REST" the words "tochange" should be "to change"
> f) Under "8. WS-Addressing" the word "programmetically" should be corrected
> as "programmatically" (2 places)
> g) Under "8. WS-Addressing > AXIS2_OPTIONS_SET_REPLY_TO(options, env,
> reply_to)" in "seperate channel. (when using dual chanel)" the words should
> be corrected as "separate" and "channel"
> h) Under "9. Writing a Module" the words "memebers", "segmement" should be
> corrected as "members" and "segment"
> i) Under "9. Writing a Module > Writing the module.xml File" the word
> "Enging" should be corrected as "Engaging"
> j) Under "Appendix A" to "Appendix D" the words "atributes", "valuses",
> "Possibe", "parmeter" (several places), "messange", "spsecifies",
> "Reciever"(several places), "prameter", "Prtocol", "elemnt"(several places),
> "Vlue", "hadler", "messgae", "asyncronous", "exchnge", "scebarios",
> "seperate", "listner", "enfdpoint", "recieve" should be corrected
> 4. It is appropriate if it mentions that to enable REST, you have to set to
> given properties in the client code. The given description does not give a
> clear idea of where to include the given code segment.
--
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]
