PS: forgot to say the logging.properties for the ear lib part should be in the classloader so in a jar basically Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau
2014/1/17 Romain Manni-Bucau <[email protected]>: > Hi > > handlers should in jvm classpath > > logging.properties can be in web-inf of wars, conf of the container or in > common.loader. putting it in ear lib part is not well defined since tomee > reuse tomcat logging logic which doesnt handle ear but it should work. > > note: reproducing it thanks to tomee mvn plugin would help us checking if it > is a bug > > Le vendredi 17 janvier 2014, ymaraner <[email protected]> a écrit : > >> If I want to specify my application JULI logging configuration inside my >> EAR >> file rather than using the TomEE config/logging.properties file, can I >> simply place a logging.properties file somewhere in my EAR? If I put it in >> the lib directory of the ear, TomEE complains that it isn't a valid jar >> file. If I put it in the META-INF directory, it seems to be ignored. What >> is >> the correct location for this? >> >> Also, if I want my logging configuration to use a custom Handler that uses >> EJB/CDI and JPA to store the logs in the database, where does the Handler >> class/jar file need to be placed? >> >> This is with the released version of TomEE plus 1.6.0. >> >> >> >> ----- >> - Tim >> -- >> View this message in context: >> http://openejb.979440.n4.nabble.com/Custom-JULI-logging-properties-and-Handler-class-for-an-EAR-tp4667219.html >> Sent from the OpenEJB User mailing list archive at Nabble.com. >> > > -- > Romain Manni-Bucau > Twitter: @rmannibucau > Blog: http://rmannibucau.wordpress.com/ > LinkedIn: http://fr.linkedin.com/in/rmannibucau > Github: https://github.com/rmannibucau > >
