|
If you were logged in you would be able to see more operations.
|
|
Sesame
Created: 07/May/09 08:49 PM
Updated: 04/Jun/09 08:27 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
2.2.4
|
| Fix Version/s: |
2.3-pr1
|
|
I found this in http://repo.aduna-software.org/svn/info.aduna/commons/lang/trunk/src/main/java/info/aduna/lang/service/ServiceRegistry.java:
logger.info("Registered service class {}", service.getClass().getName());
IMHO, This is not at all interesting for the end-user.
INFO messages are defined, according to SLF4J and apache.commons.logging to conform to the underlying logging frameworks defintion.
JAVA util logging, which can be considered a standard, says that INFO log messages must be:
"INFO is a message level for informational messages.
Typically INFO messages will be written to the console or its equivalent. So the INFO level should only be used for reasonably significant messages that will make sense to end users and system admins. This level is initialized to 800. "
http://java.sun.com/j2se/1.4.2/docs/api/java/util/logging/Level.html#INFO
I consider that sesame is hidden to the end user and besides one or two messages, the end user should not at all see it on the console. Hence I propose to remove most calls to INFO with DEBUG. I assume that was the intention after all: debugging, not informing the end user.
there are more messages, I would guess.
I cannot find programming guidelines on www.openrdf.org ruling this.
|
|
Log level has been lowered to DEBUG.
|
|
Improvement
Resolved
Minor
log level of slf4j "info" should probably not be used for debugging