What kind of docs do you have in mind? The JMX API is documented in detail here: http://logging.apache.org/log4j/2.x/log4j-core/apidocs/org/apache/logging/log4j/core/jmx/package-summary.html
In addition to API, the JMX section has pointers for connectivity, and of course docs for the GUI. To be honest, there is actually not that much that users can do via the JMX interface, at least at the moment. The interesting stuff (looking at the StatusLogger output, and reconfiguring log4j from a file or from an XML string) is covered in the JMX GUI docs. On Wednesday, October 16, 2013, Gary Gregory wrote: > Hi all: > > Reading https://issues.apache.org/jira/browse/LOG4J2-423 I wonder how > to best document JMX. Should each feature (like each appenders) (1) > document what it exposes through JMX, or, (2) should the JMX section > list all that is exposed. I'm thinking (1). > > Gary > > -- > E-Mail: garydgreg...@gmail.com <javascript:;> | > ggreg...@apache.org<javascript:;> > Java Persistence with Hibernate, Second Edition > JUnit in Action, Second Edition > Spring Batch in Action > Blog: http://garygregory.wordpress.com > Home: http://garygregory.com/ > Tweet! http://twitter.com/GaryGregory > > --------------------------------------------------------------------- > To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org<javascript:;> > For additional commands, e-mail: > log4j-dev-h...@logging.apache.org<javascript:;> > >
