Hi
you can implement org.apache.webbeans.logger.WebBeansLoggerFactory and configure it setting the system property openwebbeans.logging.factory Your implementation would surely be this one https://git-wip-us.apache.org/repos/asf?p=tomee.git;a=blob;f=container/openejb-core/src/main/java/org/apache/openejb/log/logger/Slf4jLogger.java;h=d093a40473db4ab1b83822d367a8956bc18b8e6d;hb=HEAD Romain Manni-Bucau @rmannibucau <https://twitter.com/rmannibucau> | Blog <http://rmannibucau.wordpress.com> | Github <https://github.com/rmannibucau> | LinkedIn <https://www.linkedin.com/in/rmannibucau> | Tomitriber <http://www.tomitribe.com> 2015-05-19 16:12 GMT+02:00 Lars-Fredrik Smedberg <[email protected]>: > Hi! > > As far as I understand OWB is using JUL for logging. In our production > environment we would like to control the log outputs (so they e.g. not > appear on the console). Our application uses SLF4J and a Log4j bridge to > log using different appenders depending on our requirement. Is it a good > idea to use the JUL to SLF4j bridge and then control the logging using our > log4j.properties file the same way we do with the application? Any other > good suggestions? > > Thanks > Lars-Fredrik > > -- > Med vänlig hälsning / Best regards > > Lars-Fredrik Smedberg > > STATEMENT OF CONFIDENTIALITY: > The information contained in this electronic message and any > attachments to this message are intended for the exclusive use of the > address(es) and may contain confidential or privileged information. If > you are not the intended recipient, please notify Lars-Fredrik Smedberg > immediately at [email protected], and destroy all copies of this > message and any attachments. >
