SVN main commit: Bug#218662 - change configuration logging to use config not warning

View: New views
1 Messages — Rating Filter:   Alert me  

SVN main commit: Bug#218662 - change configuration logging to use config not warning

by JAMES.SUTHERLAND :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Some parts of this message have been removed. Learn more about Nabble's security policy.

SVN main  commit: Bug#218662 - change configuration logging to use config not warning

 

https://bugs.eclipse.org/bugs/show_bug.cgi?id=218662

 

Code review: Guy (pending)

 

Changes:

Fixed to move most WARNING logging to CONFIG.  Default level is INFO, which includes

WARNING but not CONFIG, so this seems valid.  Any config related logging should

be CONFIG.

 

XML overrides, and mapped-subclass overrides were changed to config, as the user

has chosen to override these, so should not be warned about something they

chose to do.  Warnings should only occur if an error occurs, or they have

configured something wrong.

 

Several warnings were left, as these seem to be invalid configurations so should

be given warnings:

- Using @Cache in a subclass (not supported)

- Using @PrivateOwned in m-m, m-1, as not supported

- discriminator format error

- using LAZY with collection type impl, as not supported


_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@...
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev