[jboss-jira] [Red Hat JIRA] (WFLY-14160) Logging documentation needs attention and updates

James Perkins created WFLY-14160: ------------------------------------ Summary: Logging documentation needs attention and updates Key: WFLY-14160 URL: https://issues.redhat.com/browse/WFLY-14160 Project: WildFly Issue Type: Task Components: Documentation, Logging Reporter: James Perkins Assignee: James Perkins While working on an RFE that required some documentation I noticed there are several broken links in the logging documentation. While it would be simple to just fix the links I feel the logging documentation needs an overhaul and should be updated in general. For this reason I've created this issue as critical. h2. Links Several links that referred to inner-documentation links were broken long ago in the conversion to asciidoc. These need to be fixed. An example is the implicit dependencies link needs to be: {code} link:Developer_Guide.html#which-are-the-implicit-module-dependencies[implicit] {code} h2. Logging API's The logging API's should have some information on how they work. Possibly which implementation is used and if the user wants to use their own implementation which module dependencies need to be excluded. In some cases too, log4j2 is an example, there could special permissions required if a security manager is enabled. For log4j2 these are the required permissions: {code} // The getClassLoader permissions is required for the org.apache.logging.log4j.util.ProviderUtil. new RuntimePermission("getClassLoader"), // The FilePermissions is also for the org.apache.logging.log4j.util.ProviderUtil as it needs to read the JAR // for the service loader. new FilePermission("<<ALL FILES>>", "read"), // Required for the EnvironmentPropertySource System.getenv(). new RuntimePermission("getenv.*"), // Required for the SystemPropertiesPropertySource System.getProperties(). new PropertyPermission("*", "read,write"), {code} h2. How To's The How To section likely doesn't make much sense. This same documentation could be achieved in each logging API section. -- This message was sent by Atlassian Jira (v7.13.8#713008)