axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Hawkins <>
Subject Re: Memory management
Date Fri, 09 Dec 2005 10:54:10 GMT
I'm going to put this onto the web-site in the next few days but sneak 
preview ->

Many Web Services Client for C++ methods either expect or create memory 
Below is a list of rules that you must follow when developing web service 
client applications: 
v Any memory object that is passed to Web Services Client for C++ does not 
need to persist past the method for which it was required and should be 
deleted at the earliest opportunity. 
v Any memory object created and returned by Web Services Client for C++ 
should be deleted by the client application before the deletion of the web 
service that created it. Note that Windows requires that the memory object 
be deleted from within the thread that created it, otherwise you may get 
an out of bounds exception type error from the core C++ libraries. 
v Any object passed by reference (rather than value) that is used by Web 
Services Client for C++ must be created using new, and destroyed using 
v Once an object has been deleted, its pointer must be set to NULL (this 
is to ensure that the pointer is not used elsewhere).

"Stettler, Robert" <> 
08/12/2005 20:17
Please respond to
"Apache AXIS C User List"


Memory management

Does the client need to delete the memory associated with the return 
objects returned by the generated webservice methods?  Or is the memory 
managed by the axis?

The information contained in this e-mail is confidential and/or 
to Capital One and/or its affiliates. The information transmitted herewith
is intended only for use by the individual or entity to which it is 
addressed.  If the reader of this message is not the intended recipient, 
you are hereby notified that any review, retransmission, dissemination, 
distribution, copying or other use of, or taking of any action in reliance 

upon this information is strictly prohibited. If you have received this 
communication in error, please contact the sender and delete the material 
from your computer.

View raw message