right doing an ear can help even if more complicated
Romain Manni-Bucau Twitter: @rmannibucau Blog: http://rmannibucau.wordpress.com/ LinkedIn: http://fr.linkedin.com/in/rmannibucau Github: https://github.com/rmannibucau 2014-08-13 22:11 GMT+02:00 TestHorse <[email protected]>: > Hi Romain, thank you for the quick response. > > Unfortunately I do not have a sample I can share, but I think I am closer to > solving my problem. > > 1. Yes, I do have slf4j-api in WEB-INF/lib. > 2. I just meant to say all of my webapp specific logs were directed to > catalina.out instead of my "app.log" file. > > > I went back to the bare-bones Tomee install without any configuration > changes and used a .war file with every single dependent library included > (in WEB-INF/lib). This worked perfectly and actually created the "app.log" > file I wanted. Little by little, I changed any and all configuration options > until the logs disappeared. > > I believe that separating our dependent libraries (some which are EJB's) > from the webapp is the problem. In order to deploy the EJB's first due to > the dependence the webapp has on them, we added "<Deployments dir="ejbs" />" > so that the "ejbs" directory and all of the ejbs inside of it would be > deployed first. > > Since the webapp and EJB's are not deployed together anymore (required to > separate in order for client ability to update one lib/ejb at a time), it > seems the logback-classic and logback-core jar's that are still in > WEB-INF/lib are never loaded. > > If I add the required logback jars in the "ejb" directory, I suspect I will > once again see the "app.log" file created, but it will affect all of the > default, Tomee logs instead of just my webapp, right? > > > > -- > View this message in context: > http://tomee-openejb.979440.n4.nabble.com/Webapp-Logback-Logging-Does-Not-Work-Using-Tomee-Plus-1-6-0-on-Linux-tp4671110p4671120.html > Sent from the TomEE Users mailing list archive at Nabble.com.
