So how about some info about how to configure the 'new' logging - I don't really care what logging is used as long as when it changes there is a little info for those using the 'old' logging.
I just built and dropped in the jars onto my standalone test server (which I do at least once a week to see how things are going), and I now have no logging (slf4j - log4j, using conf/logging.properties). This happened before a few months ago, and I think I went in and 'fixed' it back. In an OpenEJB standalone context (I doubt I will ever need or use TomEE) what needs to be done to replace the 'conf/logging.properties' with the 'new' logging to ensure I have 'logs/openejb.log'. This is not a gripe as I am prepared to fit in to what works best for everyone else, but for info I now have over 15 standalone servers running at various locations (of which only 3 are remotely accessible, and several in production environments). I have a system tray app that 'understands' logs/openejb.log to a certain degree, and interceptors in embedded mode that do the same. I am sure if I RTFM on whatever logging is the 'default' that I would work out how to best configure it, but to just break the old logging before that happens is a bit of an ache. Andy.... Hmm, that does sound a bit like a gripe? -- View this message in context: http://openejb.979440.n4.nabble.com/Logging-tp4318587p4326876.html Sent from the OpenEJB Dev mailing list archive at Nabble.com.
