Previous Next

SET-SERIALIZED( ) method
Sets the SOAP-header-entryref object’s underlying XML from serialized XML.
Return type:
Applies to:
 
Syntax 
SET-SERIALIZED ( longchar )
longchar
A variable of type LONGCHAR that contains the serialized XML that will become the SOAP-header-entryref object.
Functions the same as SET-NODE( ), except it expects a LONGCHAR whose contents is equivalent to the serialized form of the X-noderef that would be passed to the SET-NODE( ) method. No validation is done by this method. If the contents of the LONGCHAR is not valid for the SOAP message, an error might be raised when the SOAP message is processed. If the LONGCHAR is empty, or the caller passes the Unknown value (?), the header entry will be removed from the SOAP message.
Care must be taken to distinguish between a SOAP header entry and how it is represented in ABL. A SOAP header is represented by the SOAP-header object. A SOAP header entry is represented by a SOAP-header-entryref object. The SOAP-header object maintains a list of pointers to existing SOAP-header-entryref objects that have been explicitly associated with the SOAP-header object by calling its ADD-HEADER-ENTRY( ) method.
Before you can use the SET-SERIALIZED( ) method on the SOAP-header entryref object, it must be associated with its SOAP-header object. Call the SOAP-header object’s ADD-HEADER-ENTRY( ) method prior to calling the SET-SERIALIZED method( ) or the SET-NODE method( ) for the first time. Otherwise, you will get a run-time error.
If you call either the SET-SERIALIZED( ) or SET-NODE( ) method twice in a row with the same SOAP-header-entryref, the second call will overwrite the underlying SOAP header entry created by the first call. Although you can use the same SOAP-header-entryref object to create more than one SOAP header entry, you need to call the ADD-HEADER-ENTRY() method between calls to these methods to create a new entry on the SOAP-header object’s list and associate the new entry with the current content of the SOAP-header-entryref object.

Previous Next
© 2013 Progress Software Corporation and/or its subsidiaries or affiliates.