We are running with the Bean Validation RI in an application server and doing some testing with jpa and have noticed that we see 100's of the following messages:
[5/10/10 10:41:05:715 EDT] 00000043 DefaultTraver I org.hibernate.validator.engine.resolver.DefaultTraversableResolver detectJPA Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
[5/10/10 10:41:05:786 EDT] 00000043 DefaultTraver I org.hibernate.validator.engine.resolver.DefaultTraversableResolver detectJPA Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
[5/10/10 10:41:05:837 EDT] 0000005a DefaultTraver I org.hibernate.validator.engine.resolver.DefaultTraversableResolver detectJPA Instantiated an instance of org.hibernate.validator.engine.resolver.JPATraversableResolver.
...
Is there a way to shut off the logging of this message?

Sure, set the logging level for org.hibernate.validator.engine.resolver.DefaultTraversableResolver to warn.
If you are using a lo4j.properties file it looks like this:


--Hardy

Maybe this message could be logged as DEBUG? It's the only message being logged constantly in our application.

-Anders

It doesn't seem possible to configure the log level for this in our application's log4j config, on Glassfish 3.1. Probably because it gets bundled with Glassfish.

If anyone has managed to do this, please let me know.. I haven't tried to modify the logging.properties in Glassfish, will try that next.

You have to use the logging framework which is used in your application. Hibernate Validator uses slf4j which is not bound to say logj4. You can chose your actual logging implementation. If you want to configure a particular log category you have to do so via the logging implementation you are using. Seems Glassfish is using Java logging. I think you are on the right track if you try configuration via logging.properties.


--Hardy