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,

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

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

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

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]