axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Senaka Fernando (JIRA)" <>
Subject [jira] Updated: (AXIS2C-880) Function axis2_svc_client_add_header[Alastair FETTES]
Date Fri, 04 Jan 2008 05:38:34 GMT


Senaka Fernando updated AXIS2C-880:

    Attachment: diff.txt

Hi all,

Service Client is responsible for the headers added, and we are not enforcing that. Refer
diff.txt for proposed patch.


> Function axis2_svc_client_add_header[Alastair FETTES]
> -----------------------------------------------------
>                 Key: AXIS2C-880
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>          Components: core/clientapi
>    Affects Versions: Current (Nightly)
>         Environment: Ubuntu 7.04
>            Reporter: Lahiru Gunathilake
>             Fix For: Current (Nightly)
>         Attachments: diff.txt
> <snippet>
> axis2_status_t axis2_svc_client_add_header(
>       axis2_svc_client_t*   svc_client,
>       const axutil_env_t*   env,
>       axiom_node_t*         header)
> </snippet>
> The parameter svc_client does not take responsibility for the memory allocated for header,
although it does maintain an internal pointer to the data. This can result in dangling pointer
situations if the caller deletes the memory passed using header before svc_client has a chance
to remove the header.
> Solution: Document memory ownership for parameters and return value.  Investigate the
use of pointers in the internal structure to avoid dangling pointer situations.

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:
For additional commands, e-mail:

View raw message