Community
Participate
Working Groups
is a jar implementing the validator API is on the classpath (i.e. hibernate.jar now requires this), then EclipseLink will add an event to call the validator by default, even if the Entity does not use any validator. This cause a big performance overhead in the validator calls. If we cannot change our default, then we should log a warning if the persistence.xml did not set a validator, but we decide to enabled it (warning should tell the user if they do not require validation to disable it in the persistence.xml to avoid poor performance). If we could detect if the Entity has any validation and not add the validator at all, that would be better.
Setting target and priority. See the following page for details about these fields: http://wiki.eclipse.org/EclipseLink/Development/Bugs/Guidelines
See: #391566 #447339
Created attachment 249936 [details] Proposed patch
pushed http://git.eclipse.org/c/eclipselink/eclipselink.runtime.git/commit/?id=cea25bba8d9ce92c0083ba7f15207e188173785d
The Eclipselink project has moved to Github: https://github.com/eclipse-ee4j/eclipselink