Perhaps mention of StringBuilderFormattable? It helps work around the “load the
string all at once” problem.
> On Jan 26, 2024, at 06:36, Gary Gregory wrote:
>
> Oh, I don't want to suggest this is a Lo4j issue at all. I am wondering if
> there is a pattern we should document aside from "know y
Oh, I don't want to suggest this is a Lo4j issue at all. I am wondering if
there is a pattern we should document aside from "know your third party
objects" which is not helpful for us to say. It sounds like there is
nothing for us to do.
Gary
On Fri, Jan 26, 2024, 7:16 AM Apache wrote:
> That i
That is kind of my point. Anyone who logs an object that behaves this way is
asking for trouble. It really sounds like an esoteric edge case to me. I don’t
view this as a Log4J problem as the error wouldn’t even have Log4J in the stack
trace.
Ralph
> On Jan 25, 2024, at 9:52 PM, Gary Gregory
Greetings!
We are starting 2024 with JDK 22 as it has just entered Rampdown Phase 2 [1].
And with the initial JDK 22 Release Candidates now less than 2 weeks away (Feb.
8th) [2], it is time to shift our attention to JDK 23.
After multiple rounds of incubations and preview, the Foreign Function
