Axis2/C 1.3 released

We have released Axis2/C 1.3 recently. Lot of important Jira issues are fixed in this release .This shows the enthusiasm of Axis2/C developers. Actually Axis2/C user community is growing rapidly. It can be sensed from the the mailing lists. The most important factor is that many people used it in production environments. And it is a proof of the stability and robustness of Axis2/C. I am pretty sure that 1.3 release will surely help those users who used it in their production environments and will attract new users.

Axis2/C can handle large attachments

With great deal of hard work I was able to reduce the memory consumption in large attachments.Thanks Samisa and Dumindu for valuable ideas. Uthiyashankar helped a lot to fix some problems in Windows.For complete view of the problem and solution follow this. Even though the work is tough when ever I finished such work I feel a great deal of satisfaction. And I also see now there are lots of users for Axis2/C .It generates great amount of pleasure for whole Axis2/C team. And I am also happy that I was able to fix this issue and it is shipped with 1.3 release. I am also hoping to implement caching support for large attachments. If you have any suggestions on how to do that wait a second and be kind enough to put a comment.

Axis2/C, Handling large attachment with Apache2

Dinesh has put a blog on the topic. Thanks Dinesh for that. Actually I am currently working on it. The main problem is why httpd does not release the memory after processing the request.
In Axis2/C MTOM implementation when a new buffer is read from the stream it reallocates the whole buffer for every read. Because of this string manipulation logic inside mime_parser seems bit simple. Now I am trying to manipulate the string without reallocating the whole buffer, instead keeping the buffers in an array. It seems really tough. Because string searching in two buffers seems really tricky. With a great deal of hard work I was able to send a 40M attachment using the new logic from simple_axis2_server.But httpd send only 39M. I am analyzing the problem. I noticed a huge gain in memory usage with the new logic. If you have any idea on improving this logic (inside axis2c/axiom/src/attachments/mime_parser.c) please let us know.

WS-Addressing with WSF/PHP

Web Services addressing is one of the fundamental specifications which drives Web Services platform. There are lot of reasons why you need Web Services Addressing. For a detailed description see this.

WSO2 WSF/PHP fully support WS-Addressing. It inherits this from Axis2/C Web Service engine. Adding Addressing support in WSF/PHP is really simple.

You only need to add following lines to your PHP script when you are invoking a Web Service.

Assuming some one want to set Addressing action and endpoint uri using addressing. Then first add the following.

$reqMessage = new WSMessage($requestPayloadString,
array( "to" => "http://localhost/samples/echo_service_addr.php",
"action" => "http://php.axis2.org/samples/echoString"));

Then enable WS-Addressing.

$client = new WSClient(array("useWSA" => TRUE));

Similarly you can set FaulTto, ReplyTo and other addressing parameters as well.