The User's Guide "Debugging and Logging" page (http://cxf.apache.org/docs/debugging-and-logging.html) has some bad links and refers to a nonexistent file in the distribution.
Listed by section:
The "Java SE Logging" link points to http://www.oracle.com/technology/pub/articles/hunter_logging.html, which is bad and just redirects to their main "technetwork" articles list.
Configure logging levels
> In the /etc folder of the CXF distribution there is a sample Java SE logging.properties file you can use to configure logging.
But the /etc folder of the 2.7.10 distribution does not have a `logging.properties` file. And the "/etc folder:" is a link to http://svn.apache.org/viewvc/cxf/trunk/distribution/src/main/release/etc/, which is 404 - there's no "etc/" folder there.
SLF4J and Log4J
The sections for using SLF4J and Log4J refer to adding system properties "to the classpath" with `-D`. They're not really on the classpath; maybe it would be clearer to refer to adding them to the "command line" or "Java system properties".
Also, suggesting that clients modify the system-wide logging.properties file under $JDK_HOME sounds a little extreme.
The "profiler" link is old and now redirects to the NetBeans unit testing section; profiler info is now included in the debugger page.
tcpmon and tcptrace
The "tcpmon" leading to tcpmon.dev.java.net link is dead. The whole dev.java.net subdomain is defunct.
Another dead link to dev.java.net.
The "using org.apache.cxf.jaxrs.ext.logging.atom package" pointing to http://cxf.apache.org/javadoc/latest/org/apache/cxf/management/web/logging/atom/package-summary.html is 404.
The "AtomPullServer", "ReadWriteLogStorage", and "ReadableLogStorage" links go to raw source code. Might be better from a CXF user's perspective to link to Javadoc.