Page History

...

This feature does not buffer the request and response attachment data and is completely streaming-'friendly'.

Note that in some cases the data may need to be buffered on the receiver end.

It depends on JWS with Detached Content and  JWS with Unencoded Payload options as well as on the newly introduced CXF multipart filters and works as follows.

...

However, if the receiver starts acting immediately on the attachment's InputStream, for example, the attachment data returned from the service to the client are streamed to a UI display which can activate a script then it is important that a 'bufferPayload' property is enabled on either JwsMultipartContainerRequestFilter or JwsMultipartClientResponseFilter. It will ensure that the data streams are validated first before the application gets an access to them. This property should also

The 'bufferPayload' property may also need be enabled if the multipart payload contains many attachment parts. In this case, if the receiving code is written to consume all the parts in the order different to the one the parts have been ordered in the multipart payload or if the receiver code may optionally skip reading some of the parts, then the 'bufferPayload' property must be enabled.

Here is an example showing how a Book object (represented as an XML attachment on the wire) can be secured.

...