Chin Huang

You can disable escaping for all of the variable references except for one: ``` ${testEscapingVar} ```

The pattern I suggest is make a JSP a passive view in which it does not implement any presentation logic where it sets a variable. The JSP only reads variables.

With EscapeXmlELResolverListener registered, the values from all JSP variable references will be escaped. Sometimes you don't want the values escaped. The tag `` disables escaping.

Thanks for the pull request. The [GELF format specification](https://www.graylog.org/resources/gelf-2/) allows a field value to be a [JSON](https://tools.ietf.org/html/rfc7159#page-6) number or string, so you only need to convert a field value to...

The [Java Secure Socket Extension Reference Guide](http://docs.oracle.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide.html#Customization) lists Java system properties you can set to configure the truststore, keystore and keystore password. Assuming you have a CA certificate in a...

If you don't want to modify the Java default truststore cacerts file, you can set the [javax.net.ssl.trustStore](http://docs.oracle.com/javase/8/docs/technotes/guides/security/jsse/JSSERefGuide.html#CustomizingStores) system property to use another truststore.

Logback by itself will continue if there's something wrong in its configuration. Did you mean your Spring Boot application fails to start? The Spring Boot developers intended for the application...

What version of the com.rabbitmq:amqp-client dependency are you running? Version 4.0.0 introduced a [change to ForgivingExceptionHandler.java](https://github.com/rabbitmq/rabbitmq-java-client/pull/180/files#diff-26d2450f5ae34982e6036c9f9dde84b5be67d93dbfb83ee370c84647ec80b74a) to log the error. In previous versions, it did nothing with the error. As...

I'm surprised your workaround mitigates the issue. It's a fundamental design flaw. The logger invokes amqp-client to send messages. The amqp-client invokes the logger to log errors. This circular dependency...

There is already issue #1785 to document the `{vault}` decryptor.