jeremiahjstacey

@kwwall The way I would want to fix this would be to remove the custom property file that I used before I understood the java LogManager configuration. Would we correct...

I think that works. The changes I think that implies would be: * esapi-java-logging.properties files are removed from the baseline and configuration delivery * The static method behavor in JavaLogFactory...

https://github.com/ESAPI/esapi-java-legacy/wiki/Configuring-the-JavaLogFactory Generated, and stub content is provided based on previous comment.

Might be worth pointing out that the netty 4.0.24-Final version is 10 years old and has no direct dependencies on ESAPI https://mvnrepository.com/artifact/io.netty/netty-all/4.0.24.Final https://repo1.maven.org/maven2/io/netty/netty-all/4.0.24.Final/netty-all-4.0.24.Final.pom I've poked through several of the netty...

Looking at the stack trace, and the implementation of the DefaultEncoder class, my guess is that you're missing a piece of configuration. https://github.com/ESAPI/esapi-java-legacy/blob/develop/src/main/java/org/owasp/esapi/reference/DefaultEncoder.java Line 118 is trying to iterate the...

If this method was created to fill a void of the java runtime that has since been provided, then I think it's worth considering deprecating `DefaultRandomizer.getRandomGUID()` in favor of the...

@xeno6696 without digging into it too much I'd suggest checking what the PushbackString would give you in a test case. I have it in my head that it defaults to...

Although your project may not call the ESAPI logging API directly, it is still referenced at runtime and is required by the library components you are using. ESAPI Logging is...

This is true for all of the *LogFactory implementations. The ESAPI logger is enabled to support all ESAPI Logging levels by default; however, it will filter the log event to...

You're right, @kwwall. There is a chance for inconsistency, which is why I left it as ALL as a hard-coded attribute until now. To your point > figure out how...