The following table summarizes the available ABL elements and how they can help you to manage memory for SOAP headers.

Table 1. ABL to manage object memory for SOAP headers
ABL element Applied to object Deletes the ABL object Deletes all underlying XML DOM objects
Setting the lDeleteOnDoneOUTPUT parameter of the request header handler to TRUE (see the Defining header handlers SOAP header object Yes Yes
DELETE OBJECT statement SOAP header object Yes Yes
X-document object Yes Yes
SOAP header-entryref object Yes No
X-noderef object Yes No
DELETE-HEADER-ENTRY( ) method SOAP header-entryref object No Yes
DELETE-NODE( ) method X-noderef object No Yes1
CAUTION: Be sure that you always delete the underlying XML for a SOAP header-entryref object before you delete the SOAP header-entryref object itself. If you lose all reference to the underlying XML before deleting it, its memory becomes lost to your application. If this occurs as part of an iterative process, it represents a memory leak that could cause your application to crash.
1 This includes any child sub-trees of the deleted X-noderef object.