Return-Path: Delivered-To: apmail-ws-axis-c-user-archive@www.apache.org Received: (qmail 22463 invoked from network); 19 Jun 2007 10:43:51 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 19 Jun 2007 10:43:51 -0000 Received: (qmail 70195 invoked by uid 500); 19 Jun 2007 10:43:54 -0000 Delivered-To: apmail-ws-axis-c-user-archive@ws.apache.org Received: (qmail 70174 invoked by uid 500); 19 Jun 2007 10:43:54 -0000 Mailing-List: contact axis-c-user-help@ws.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: "Apache AXIS C User List" Reply-To: "Apache AXIS C User List" Delivered-To: mailing list axis-c-user@ws.apache.org Received: (qmail 70156 invoked by uid 99); 19 Jun 2007 10:43:53 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jun 2007 03:43:53 -0700 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests= X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: local policy) Received: from [194.31.92.43] (HELO drb9.drb.insel.de) (194.31.92.43) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 19 Jun 2007 03:43:49 -0700 Received: from fspc.drb.insel.de (fspc.DrB.insel.DE [194.31.92.39]) by drb9.drb.insel.de (8.13.5/8.13.5) with ESMTP id l5JAhRks006753 for ; Tue, 19 Jun 2007 12:43:27 +0200 (MEST) Date: Tue, 19 Jun 2007 12:43:23 +0200 To: "Apache AXIS C User List" Subject: Re: [AXIS2C] memory management From: "Dr. Florian Steinborn" Organization: Dr. Brunthaler GmbH Content-Type: text/plain; format=flowed; delsp=yes; charset=iso-8859-15 MIME-Version: 1.0 References: <46776EE3.2020600@wso2.com> <46779FBF.8030507@wso2.com> Content-Transfer-Encoding: 7bit Message-ID: In-Reply-To: <46779FBF.8030507@wso2.com> User-Agent: Opera Mail/9.21 (Linux) X-Virus-Checked: Checked by ClamAV on apache.org Hi Samisa, >> >> 3. Do I understand correctly, nobody else frees the memory if not the >> user does it? Cannot imagine that - all the generated services would be >> giantic memory holes... > The model is that the user got to free it. The notion of "user got to > free it" makes sense, as the user has control over the lifetime of the > struct instance. I think we had a misunderstanding. Of course the user has to free the memory that he allocates. I had a deeper look into the generated free-functions and see that the axis2_skel__getString method is called in the "invoke" part and the memory is freed by the automatic call of axis2_getString_free(). If there is additional memory allocated by the user he has to free it himself. I see. Thanks, Flori --------------------------------------------------------------------- To unsubscribe, e-mail: axis-c-user-unsubscribe@ws.apache.org For additional commands, e-mail: axis-c-user-help@ws.apache.org