PI80273: INCLUSIVE=FALSE OF @DECIMALMIN AND @DECIMALMAX DOESN'T WORK AS EXPECTED.

9.0.0.5: WebSphere Application Server traditional V9.0 Fix Pack 5
9.0.0.6: WebSphere Application Server traditional V9.0 Fix Pack 6
9.0.0.7: WebSphere Application Server traditional V9.0 Fix Pack 7
9.0.0.8: WebSphere Application Server traditional V9.0 Fix Pack 8
9.0.0.9: WebSphere Application Server traditional V9.0 Fix Pack 9
9.0.0.10: WebSphere Application Server traditional V9.0 Fix Pack 10
9.0.0.11: WebSphere Application Server traditional V9.0 Fix Pack 11
9.0.5.0: WebSphere Application Server traditional Version 9.0.5 Refresh Pack
9.0.5.1: WebSphere Application Server traditional Version 9.0.5 Fix Pack 1
9.0.5.2: WebSphere Application Server traditional Version 9.0.5 Fix Pack 2
9.0.5.3: WebSphere Application Server traditional Version 9.0.5 Fix Pack 3
9.0.5.4: WebSphere Application Server traditional Version 9.0.5 Fix Pack 4
9.0.5.5: WebSphere Application Server traditional Version 9.0.5 Fix Pack 5
WebSphere Application Server traditional 9.0.5.6
9.0.5.7: WebSphere Application Server traditional Version 9.0.5 Fix Pack 7
9.0.5.8: WebSphere Application Server traditional Version 9.0.5.8
9.0.5.9: WebSphere Application Server traditional Version 9.0.5.9
9.0.5.10: WebSphere Application Server traditional Version 9.0.5.10
9.0.5.11: WebSphere Application Server traditional Version 9.0.5.11

APAR status

• Closed as program error.

Error description

• Even if we set inclusive=false for @DecimalMin or @DecimalMax,
  the setting seems to be ignored.
  ---------------------------
  public class MyForm {
      @DecimalMax(value = "10", message="sample1 should be not be
  greater than 10. (10=<10)")
      private BigDecimal sample1;
  
      @DecimalMax(value = "10", inclusive=false, message="sample2
  should be less than 10. (10<10)")
      private BigDecimal sample2;
  ---------------------------
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server Bean Validation feature using the    *
  *                  @DecimalMin and @DecimalMax constraints.    *
  ****************************************************************
  * PROBLEM DESCRIPTION: Bean Validation 1.1 @DecimalMin and     *
  *                      @DecimalMax constraints' inclusive      *
  *                      property is not working.                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  The @DecimalMin and @DecimalMax constraints for Bean
  Validation 1.1 are not properly honoring the inclusive
  property. The default inclusive = true behavior is always
  occurring, even when inclusive is set to false.
  

Problem conclusion

• The Bean Validation 1.1 code has been updated to correctly
  check the inclusive property before checking if a @DecimalMin
  or @DecimalMax constraint is valid.
  
  The fix for this APAR is currently targeted for inclusion in
  fix pack 9.0.0.5.  Please refer to the Recommended Updates
  page for delivery information:
  http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R900 PSY

     UP