I'll certainly be trying 1.1.1 when it comes out.
But in this case I'm sure that wouldn't help. In my app, I have:
System.out.println: nothing appears
java.util.logging.Logger: nothing appears
Servlet.log(): nothing appears
When all my other apps start up they leave all sorts of chatter about mapping
entities, starting message queues, deploying Tomcat, etc. When these two apps
deploy, there is NOTHING on the console. I don't even know that they are
deploying.
So I'm 99.9% certain that @Logger wouldn't make any difference because none of
Seam's other messages are showing up either.
As I said, log4j is fragile junk. The most important feature of a logging
system is to log. I have checked over every config file I can think of
checking and I can't see any problem.
I'm certain that this is related to virtual hosts and maybe to the way Tomcat
handles virtual hosts. I am getting log messages just fine on my other machine
here that has only one host entry in the server.xml file. I think I've seen
strange behavior like this in Tomcat with virt. hosts before.
None of this excuses it; if it takes me a day to figure out why
logger.severe("hello") isn't leaving a message, that is broken. Loggers are
debugging tools.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4001864#4001864
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4001864
_______________________________________________
jboss-user mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/jboss-user
