Re: Question on memory allocation / deallocation for AXIS_MALLOC

On 9/26/07, Sathya Raghunathan <pappu.raghunathan-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:

I am seeing that there is a function call adb_pInterchange_free() that the wsdl2c code generator has generated. But where exactly should we call this? The service function has to return the object. After this, where can the memory be deallocated?

In the service all the  objects  you created will be freed by the  generated code after the objects are serialized in to an xml. So you dont need to think about it.

Thanks
Sathya

On 9/26/07, Sathya Raghunathan < pappu.raghunathan-Re5JQEeQqe8AvxtiuMwx3w@xxxxxxxxxxxxxxxx> wrote:

Hi

 

I have a question on memory allocation and deallocation:

 

Suppose in my service function, I have created an object of a particular type (for ex: adb_pInterchange_t* myInt = adb_pInterchange_create(env);)

 

This particular function uses AXIS_MALLOC to allocate memory for that particular object.

_pInterchange = (adb_pInterchange_t *) AXIS2_MALLOC(env->allocator, sizeof(adb_pInterchange_t));

 

After returning this as the soap response message, how will memory be deallocated? Is it taken care of automatically ? Or since we create this object inside the service function to fill the business logic, should we deallocate it manually ? If so, where exactly should we deallocate this memory?

 

Please clarify.

 

Thanks

Sathya