Dear all, currently the Infinispan log messages "fall" in the categories named from the originating class. While this isfine for TRACE/DEBUG messages, there are some high-level INFO events which warrant their own specific categories. I think that user-triggered events (such as JMX ops) should also be treated like this. Examples:
org.infinispan.CLUSTER (for important view change, state transfer and rebalancing messages) org.infinispan.CACHE (for cache lifecycle events) org.infinispan.PERSISTENCE What do you think ? Any other suggestions ? Tristan _______________________________________________ infinispan-dev mailing list infinispan-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/infinispan-dev
