| [eclipselink-dev] Fix for bug 245268 - Conforming should throw exception when parameter type incorrect |
|
The following fix has been checked in, and was previously
reviewed. Bug 245268 - Conforming should throw exception when parameter type incorrect https://bugs.eclipse.org/245268 (Patch files have also been uploaded to this bug) Previously reviewed by: Chris Delahunt Problem: ParameterExpression > validateParameterValueAgainstMapping does not get called when ParameterExpression > getValue is invoked, where baseExpression is null (no nesting) Changes: - Refactored ParameterExpression > validateParameterValueAgainstMapping to allow validation against either the baseExpression or localBase - Changed calls to ParameterExpression > validateParameterValueAgainstMapping - Added call to ParameterExpression > validateParameterValueAgainstMapping within ParameterExpression > getValue where baseExpression is null (no nesting) Code Review: Not Required (previously reviewed) Testing: LRG (OK) Changed QueryParameterForOneToOneValidationTest to support conforming scenario, made changes to ExceptionValidationTestSuit to add in test for conforming scenario. --
 David Minsky | Senior Member of Technical Staff | (613) 288-4605 Oracle Server Technologies | Sustaining Engineering 45 O'Connor Street, Suite 400, Ottawa, Ontario, Canada K1P 1A4 |