Re: [Axis2[ Time for a release?
On Sun, Dec 6, 2009 at 8:27 AM, Selvaratnam Uthaiyashankar uthaiyashan...@gmail.com wrote: On Fri, Dec 4, 2009 at 11:13 PM, Samisa Abeysinghe sam...@wso2.com wrote: I meant to say, Axis2! Samisa... On Fri, Dec 4, 2009 at 11:08 PM, Samisa Abeysinghe sam...@wso2.com wrote: Folks, I looked at the Jiras after a lng time and seems that there are quite a number of them as well as few ones with patches from users. May be it is a good time to fire up a new release. Thoughts are welcome. +1. I'll go through the Jira and fix them. What will be the version number? 1.7.0? Yes, I think it should be 1.7, as we have few new features. Samisa... Regards, Shankar Thanks, Samisa... -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company -- S.Uthaiyashankar Software Architect WSO2 Inc. http://wso2.com/ - The Open Source SOA Company -- Samisa Abeysinghe Director, Engineering - WSO2 Inc. http://www.wso2.com/ - The Open Source SOA Company
Re: DLL path for libTestCases_t.so is set to libTestCases.so
On Sat, Dec 5, 2009 at 7:46 AM, gsherw...@att.net wrote: Samisa, Thanks for the response. I mentioned the _t because when I posted the message, the ONLY difference between the two services was their names. One has the _t and the other does not. So it seemed likely to me that the different behavior was related to their different names. This is not a big problem for me because I think I have a workaround. I guessed that the Axis2/C team would either recognize what's happening here, or would want to understand it sometime. Thank you for the input. I think there might be a bug/issue in handling the service names with special characters such as '_'. Need to look into this. If you could raise a Jira, that might be useful. Samisa...
client side memory management
I am looking at the hello.c sample and seeing a lot of things that are never freed. I am also not seeing any rules stated on who is responsible for freeing memory on things. For example, in the hello.c code an axis2_options_t *options is created but at no point is it freed. Is it automatically freed when axutil_env_free() is called or is that an oversight in the example? Another example is in the build_om_request method, it looks like axiom_element_create() creates both the axiom_node_t* greet_om_node and axiom_element_t * greet_om_ele, but at no point do I see either being freed. Does the axis2_svc_client_send_receive() free them or is this also an oversight in the example? Sam
Getting the HTTP Status Codes
I am working with the Axis2/C client. The web server can reply with a number of different HTTP Status Codes, HTTP_UNAUTHORIZED or HTTP_MOVED_PERMANENTLY. It looks like in both cases env-error-error_number is AXIS2_ERROR_HTTP_CLIENT_TRANSPORT_ERROR (74). Is there any way to get to the actual HTTP Status Code? Sam
Re: client side memory management
Sam Carleton wrote: I am looking at the hello.c sample and seeing a lot of things that are never freed. I am also not seeing any rules stated on who is responsible for freeing memory on things. See whether this would help [1] Thanks, Damitha [1] http://damithakumarage.wordpress.com/2009/03/07/memory-handling-conventions-in-axis2c/ For example, in the hello.c code an axis2_options_t *options is created but at no point is it freed. Is it automatically freed when axutil_env_free() is called or is that an oversight in the example? Another example is in the build_om_request method, it looks like axiom_element_create() creates both the axiom_node_t* greet_om_node and axiom_element_t * greet_om_ele, but at no point do I see either being freed. Does the axis2_svc_client_send_receive() free them or is this also an oversight in the example? Sam -- __ Damitha Kumarage Technical Lead; WSO2 Inc. Oxygenating the Web Service Platform; http://www.wso2.com/ blog: http://damithakumarage.wordpress.com/ __
