When using Streaming, if you receive a SOAP message of MIME Multipart/Related structure containing an attachment, the MIME body contained in the SOAP message might be output to a temporary file and not to the memory. Whether the MIME body contained in the SOAP message is extracted to the memory or output to the temporary file is determined based on the value specified in the parseEagerly, type of MIME parts, and the MIME body size.

The following table lists the output destination of the MIME body contained in the SOAP message:

Table 32-2 Output destination of MIME bodies contained in SOAP messages

No.	Type of MIME Parts	Value specified in parseEagerly	MIME body size	Output destination of MIME body
1	Root Part	--	Greater than the threshold value #	Output to the temporary file instead of deploying to the memory.
2			Less than or equal to the threshold value#	Deploy to the memory instead of an output to a temporary file.
3	Attachment Part	true	Greater than threshold #	Outputs to the temporary file instead of extracting to the memory.
4			Below the threshold#	Extracts to the memory instead of performing output to a temporary file.
5		false	None	Outputs neither to a temporary file nor to the memory.

Legend:

--: The specified value does not have an effect on the output destination of the MIME body.

#

Threshold is the value of the memoryThreshold element of the com.sun.xml.ws.developer.StreamingAttachment annotation or the memoryThreshold value of the com.sun.xml.ws.developer.StreamingAttachmentFeature class.

Determine whether to output the MIME body included in the SOAP message to the temporary file after evaluating MIME bodies of each MIME part. If there is one root part and two attachment parts in the SOAP message of the MIME Multipart/Related structure that contains the received attachment, the evaluation to determine whether to output a temporary file will be executed three times.

Organization of this section

32.3.1 Naming convention

32.3.2 Output and Deletion

32.3.3 How to estimate