get rid of a stack trace
because some amazing geniuses on stackoverflow who know much more than me about Hibernate are obsessing over this DEBUG-level log message
This commit is contained in:
parent
18ca4b41c1
commit
52e80f76b5
|
@ -168,7 +168,7 @@ public class BytecodeProviderImpl implements BytecodeProvider {
|
|||
findAccessors( clazz, getterNames, setterNames, types, getters, setters );
|
||||
}
|
||||
catch (InvalidPropertyAccessorException ex) {
|
||||
LOG.unableToGenerateReflectionOptimizer( clazz.getName(), ex );
|
||||
LOG.unableToGenerateReflectionOptimizer( clazz.getName(), ex.getMessage() );
|
||||
return null;
|
||||
}
|
||||
|
||||
|
@ -232,7 +232,7 @@ public class BytecodeProviderImpl implements BytecodeProvider {
|
|||
findAccessors( clazz, propertyAccessMap, getters, setters );
|
||||
}
|
||||
catch (InvalidPropertyAccessorException ex) {
|
||||
LOG.unableToGenerateReflectionOptimizer( clazz.getName(), ex );
|
||||
LOG.unableToGenerateReflectionOptimizer( clazz.getName(), ex.getMessage() );
|
||||
return null;
|
||||
}
|
||||
|
||||
|
|
|
@ -1843,9 +1843,9 @@ public interface CoreMessageLogger extends BasicLogger {
|
|||
void unableToDetermineCockroachDatabaseVersion(String minimumVersion);
|
||||
|
||||
@LogMessage(level = DEBUG)
|
||||
@Message(value = "Unable to create the ReflectionOptimizer for [%s]",
|
||||
@Message(value = "Unable to create the ReflectionOptimizer for [%s]: %s",
|
||||
id = 513)
|
||||
void unableToGenerateReflectionOptimizer(String className, @Cause Throwable cause);
|
||||
void unableToGenerateReflectionOptimizer(String className, String cause);
|
||||
|
||||
@LogMessage(level = WARN)
|
||||
@Message(value = "PostgreSQL JDBC driver classes are inaccessible and thus, certain DDL types like JSONB, JSON, GEOMETRY can not be used.",
|
||||
|
|
Loading…
Reference in New Issue