Maybe, if
global logging level is less informative than required one,
eclipse link should overwrite this global?
I mean spring
wants FINE, Eclipselink is set to FINER, then FINER should
be result?
Thank you,
Radek
On 8/13/14, 4:57 PM, Radek Menšík wrote:
I Have described the problem here:
http://stackoverflow.com/questions/25264305/eclipselink-is-not-logging-finer-or-finest-level-only-fine
Based on the code involved[1], I'd say it is a bug in
Spring. They should be using "
eclipselink.logging.level.sql=FINE" instead of setting
global logging level to FINE if they want to just shown SQL
statements (not only to avoid unnecessary output but to also
allow better user logging configuration).
--lukas
[1]: http://grepcode.com/file/repo1.maven.org/maven2/org.springframework/spring-orm/4.0.5.RELEASE/org/springframework/orm/jpa/vendor/EclipseLinkJpaVendorAdapter.java#EclipseLinkJpaVendorAdapter.getJpaPropertyMap%28%29
Radek
_______________________________________________
eclipselink-users mailing list
eclipselink-users@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/eclipselink-users