axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Supun Kamburugamuva (JIRA)" <>
Subject [jira] Commented: (AXIS2C-452) Attachment problem
Date Mon, 12 Mar 2007 10:03:09 GMT


Supun Kamburugamuva commented on AXIS2C-452:

I have fixed the problem with empty attachments. The problem was in the axiom/src/attachments/data_handler.c
file. When an empty file is given axiom_data_handler_read_from function's while loop ran without
stopping. I have corrected this problem so that when a empty file is given it returns a empty

> Attachment problem
> ------------------
>                 Key: AXIS2C-452
>                 URL:
>             Project: Axis2-C
>          Issue Type: Bug
>    Affects Versions: 0.95
>         Environment: Linux
>            Reporter: yong yang
>         Assigned To: Dinesh Premalal
>             Fix For: 1.0.0
>         Attachments: axis2.c, axis2.h, client.c, test.c
> 1)send attachment
> for example, the client will attach three files to the web service. 
> a) The first file exists and is not empty
> b) The second file doesn't exist or it is empty.
> c) The third file exists and is not empty
> when the server receives the SOAP message, it will try to detach
> these files. But the server only can detach the first file and can
> not detach the third file. When I used the TCP MONITOR to trace the
> SOAP message, the first MIME contains the content of the first file;
> the second MIME is empty; the third MIME contains the content of the
> third file. I also check what is the content in corresponding binary
> node, I found the binary node in both second and third attachment
> node are NULL.
> 2)send back attachment
> If the server would like to send back the attachment to the client in case of SEND-AND-RECEIVE
message pattern, it seems that the server can not attach these files. When I used the TCP
monitor to trace the SOAP message, no any MIME in the SOAP reply even if I enable the MTOM
options in the server program. When I read some doucments, it seems tha tthe OPTIONS only
can associate with CLIENT. How can I associate the OPTIONS with the server as well?

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