On a tangent, I'm considering releasing a CF simpl...
# lucee
s
On a tangent, I'm considering releasing a CF simple logger component to the public domain. Should I publish on github, bitbucket, or something else? This component uses native CF and "standard" java, with no dependencies, which was why I wrote it. (I was suffering from jar wars which I have to imagine others suffer from as well)
a
GitHub and ForgeBox.
👍 3
That said, for solving the same issue (IE: not having to rely on Lucee's logging), LogBox is a pretty good solution. It's mostly decoupled from anything else *Box, and the few touchpoints are easily circumvented.
But it did require a bit of dicking around to get it working.
s
My requirement was a rolling file appender, which lucee removed from it's version of log4j2 - I assume for speed. log4j works great for me in CF because they use standard log4j2, but I spend too many hours attempting to find the working recipe to swap out lucee log4j2 with apache log4j2 - hence, my jar wars reference. I guess I assumed LogBox was a wrapper on top of log4j so I did not look. 😞
a
No it's all native CFML. However it's rolling file appender had the race condition issues under any sort of load. I think Luis has since fixed that though (too late for us: we rolled out own).
s
I'll take a look before I publish "yet another already written component" and see what and how it does it's magic.
a
I was not meaning you should not publish it. You should. My comment was more to other people reading the thread.
s
I did not take your comment that way, no worries.
👍 1