public class MockServerHttpResponse extends AbstractServerHttpResponse
AbstractServerHttpResponse for use in tests without
an actual server.
By default response content is consumed in full upon writing and cached
for subsequent access, however it is also possible to set a custom
writeHandler.
| Modifier and Type | Field and Description |
|---|---|
private <any> |
body |
private java.util.function.Function<<any>,<any>> |
writeHandler |
logger| Constructor and Description |
|---|
MockServerHttpResponse() |
MockServerHttpResponse(DataBufferFactory dataBufferFactory) |
| Modifier and Type | Method and Description |
|---|---|
protected void |
applyCookies()
Add cookies from
AbstractServerHttpResponse.getHeaders() to the underlying response. |
protected void |
applyHeaders()
Apply header changes from
AbstractServerHttpResponse.getHeaders() to the underlying response. |
protected void |
applyStatusCode()
Write the status code to the underlying response.
|
private static java.lang.String |
bufferToString(DataBuffer buffer,
java.nio.charset.Charset charset) |
<any> |
getBody()
Return the response body or an error stream if the body was not set.
|
<any> |
getBodyAsString()
Aggregate response data and convert to a String using the "Content-Type"
charset or "UTF-8" by default.
|
<T> T |
getNativeResponse()
Return the underlying server response.
|
<any> |
setComplete()
Indicate that message handling is complete, allowing for any cleanup or
end-of-processing tasks to be performed such as applying header changes
made via
HttpMessage.getHeaders() to the underlying HTTP message (if not
applied already). |
void |
setWriteHandler(java.util.function.Function<<any>,<any>> writeHandler)
Configure a custom handler to consume the response body.
|
protected <any> |
writeAndFlushWithInternal(<any> body)
Write to the underlying the response, and flush after each
Publisher<DataBuffer>. |
protected <any> |
writeWithInternal(<any> body)
Write to the underlying the response.
|
addCookie, beforeCommit, bufferFactory, doCommit, doCommit, getCookies, getHeaders, getStatusCode, getStatusCodeValue, isCommitted, setStatusCode, setStatusCodeValue, writeAndFlushWith, writeWithprivate <any> body
private java.util.function.Function<<any>,<any>> writeHandler
public MockServerHttpResponse()
public MockServerHttpResponse(DataBufferFactory dataBufferFactory)
public void setWriteHandler(java.util.function.Function<<any>,<any>> writeHandler)
By default, response body content is consumed in full and cached for subsequent access in tests. Use this option to take control over how the response body is consumed.
writeHandler - the write handler to use returning Mono<Void>
when the body has been "written" (i.e. consumed).public <T> T getNativeResponse()
AbstractServerHttpResponseNote: This is exposed mainly for internal framework use such as WebSocket upgrades in the spring-webflux module.
getNativeResponse in class AbstractServerHttpResponseprotected void applyStatusCode()
AbstractServerHttpResponseapplyStatusCode in class AbstractServerHttpResponseprotected void applyHeaders()
AbstractServerHttpResponseAbstractServerHttpResponse.getHeaders() to the underlying response.
This method is called once only.applyHeaders in class AbstractServerHttpResponseprotected void applyCookies()
AbstractServerHttpResponseAbstractServerHttpResponse.getHeaders() to the underlying response.
This method is called once only.applyCookies in class AbstractServerHttpResponseprotected <any> writeWithInternal(<any> body)
AbstractServerHttpResponsewriteWithInternal in class AbstractServerHttpResponsebody - the publisher to write withprotected <any> writeAndFlushWithInternal(<any> body)
AbstractServerHttpResponsePublisher<DataBuffer>.writeAndFlushWithInternal in class AbstractServerHttpResponsebody - the publisher to write and flush withpublic <any> setComplete()
ReactiveHttpOutputMessageHttpMessage.getHeaders() to the underlying HTTP message (if not
applied already).
This method should be automatically invoked at the end of message processing so typically applications should not have to invoke it. If invoked multiple times it should have no side effects.
setComplete in interface ReactiveHttpOutputMessagesetComplete in class AbstractServerHttpResponseMono that indicates completion or errorpublic <any> getBody()
public <any> getBodyAsString()
private static java.lang.String bufferToString(DataBuffer buffer, java.nio.charset.Charset charset)