A: 

I'm not sure if "NONE" is a valid level in log4j (maybe it is). You could try changing the Level to "OFF" (or at least "WARN" or "ERROR").

http://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/Level.html

Andy White
In fact it makes no difference if i put DEBUG, INFO, FOO etc. The hibernate still flooding the IDE console. Thats is the point. Thank you anyway.
Warlei
A: 

I think Tomcat expects a log4j.properties file in WEB-INF/classes. Have you tried converting the .xml to that?

sblundy
No, I din´t. I´ll going to do it now. Thank you.
Warlei
A: 

Could also be the Tomcat internal logger, especially if it's logging connection info and select statements.

sblundy
It really makes sense. But because the container is encapsulated as a runtime in the Eclipse environment I´m not so sure about the correct way to do it. So, I followed the instructions suggested to made the modifications and made them in the tomcat home directory, but without effects. In doubt, I created a new runtime and publish the project under it and still got floods in the console. Thank you anyway.
Warlei