On 4 February 2018 at 23:35, Ralph Goers wrote:
> Well I have good news and bad news. The bad news is that I forgot my wife
> and I were having people over for the super bowl so I didn’t have as much
> time as I had hoped and I wasn’t able to run the Log4j 2.11.0 release build.
>
No worries!
>
Chandra,
Yes it is a new project. I’ve been working on it for quite some time. I
developed something like it for my former employer many years ago and it was
one of my primary motivations for starting Log4j 2. I am using this project at
my current employer.
A container is not required to perfo
Hi Remko,
+1 for the top page feedback. This is the first time I’m looking at this (is
this a new project under log4j?).
Also, is a container (tomcat or others ) a requirement? if it is I do not see
it in the requirements section. I assumed it was an api either using or built
on top of log4j2
Remko,
Thanks for all the good feedback! That is exactly what I was looking for.
I won’t answer the questions you posed here. Instead, I will try to correct the
web site to see if it does the job.
Ralph
> On Feb 5, 2018, at 8:04 AM, Remko Popma wrote:
>
> About the web site, the project seem
About the web site, the project seems to have components, but the component
links in the left-hand navigation menu are not very useful:
If you click on "Audit API" for example, only some standard Maven-generated
component links/pages are visible, no javadoc or sources in the Component
Reports.
Also
Some first impression feedback:
Top page:
I think it is worth explaining the motivation/use case for audit logging
here. What is "audit logging"? How is audit logging different from "normal"
logging? What kind of applications would want to use audit logging and why?
What are audit events? How do a
