Externalizable Objects in Flex Scripts

When recording a Flex application, information is usually passed between the client and server using known serialization methods (AMF). If this is the case, VuGen creates a flex_amf_call and both the request and response are parsed.

However, when a given AMF object uses a custom serialization method (externalizable), VuGen automatically issues a warning. This warning displays details about the exception, as well as recommended actions for resolving it.

The following are some examples of the exceptions that the generated script may include when an AMF object uses a custom serialization method:

  • Request and response not parsed. This exception is automatically displayed in the Errors pane when the Warnings button is selected, and the Define Available Categories filter is set to All or Code Generation Notification. Details about the exception are listed, as well as recommended actions. For details, see Errors Pane.

  • Request parsed but response is not parsed. VuGen generates a IsParseResponse=No statement. Additionally, VuGen issues a warning that is automatically displayed in the Errors pane when the Warnings button is selected, and the Define Available Categories filter is set to All or Code Generation Notification. The list of warnings displays details about the exception, as well as recommended actions. For details, see Errors Pane.

For details on configuring the Recording Options > Flex > Externalizable Objects Node, see Flex > Externalizable Objects Recording Options.

The following flowchart illustrates the steps to resolve externalizable objects in Flex scripts:

Back to top

See also: