Consistent final logger fields

This commit is contained in:
Juergen Hoeller
2016-10-04 23:00:36 +02:00
parent 684d6ab553
commit cfa0f6c84b
10 changed files with 21 additions and 26 deletions

View File

@@ -42,7 +42,7 @@ import org.springframework.web.util.WebUtils;
*/
public class OriginHandshakeInterceptor implements HandshakeInterceptor {
protected Log logger = LogFactory.getLog(getClass());
protected final Log logger = LogFactory.getLog(getClass());
private final Set<String> allowedOrigins = new LinkedHashSet<>();

View File

@@ -55,7 +55,7 @@ public abstract class AbstractXhrTransport implements XhrTransport {
}
protected Log logger = LogFactory.getLog(getClass());
protected final Log logger = LogFactory.getLog(getClass());
private boolean xhrStreamingDisabled;
@@ -71,11 +71,9 @@ public abstract class AbstractXhrTransport implements XhrTransport {
* An {@code XhrTransport} can support both the "xhr_streaming" and "xhr"
* SockJS server transports. From a client perspective there is no
* implementation difference.
*
* <p>Typically an {@code XhrTransport} is used as "XHR streaming" first and
* then, if that fails, as "XHR". In some cases however it may be helpful to
* suppress XHR streaming so that only XHR is attempted.
*
* <p>By default this property is set to {@code false} which means both
* "XHR streaming" and "XHR" apply.
*/