PM86762: USING @REPORTASSINGLEVIOLATION WITH CUSTOM CONSTRAINT RESULTS IN ERRORS.

8.5.5.1: WebSphere Application Server V8.5.5 Fix Pack 1
8.5.5.2: WebSphere Application Server V8.5.5 Fix Pack 2
8.5.5.3: WebSphere Application Server V8.5.5 Fix Pack 3
8.5.5.4: WebSphere Application Server V8.5.5 Fix Pack 4
8.5.5.5: WebSphere Application Server V8.5.5 Fix Pack 5
8.5.5.6: WebSphere Application Server V8.5.5 Fix Pack 6
8.5.5.7: WebSphere Application Server V8.5.5 Fix Pack 7
8.5.5.8: WebSphere Application Server V8.5.5 Fix Pack 8
8.5.5.9: WebSphere Application Server V8.5.5 Fix Pack 9
8.5.5.10: WebSphere Application Server V8.5.5 Fix Pack 10
8.5.5.11: WebSphere Application Server V8.5.5 Fix Pack 11
8.5.5.12: WebSphere Application Server V8.5.5 Fix Pack 12
8.5.5.13: WebSphere Application Server V8.5.5 Fix Pack 13
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14
8.5.5.15: WebSphere Application Server V8.5.5 Fix Pack 15
8.5.5.14: WebSphere Application Server V8.5.5 Fix Pack 14

APAR status

• Closed as program error.

Error description

• User created several custom composite constraints for use with
  the Bean Validation framework.  These constraints used the
  annotation @ReportAsSingleViolation to override the violation
  reporting from the individual constraints.
  
  When a Java class where several fields are annotated with these
  custom constraints, it showed unusual behavior.  If a field
  results in a  violation, all remaining fields are also flagged
  as violation.
  
  This issue appears to be related to the following BVAL JIRA:
  https://issues.apache.org/jira/browse/BVAL-116
  

Local fix

• No work around can be done at this time,
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:  All users of IBM WebSphere Application      *
  *                  Server V8.5.0 and V8.5.5 who make use of    *
  *                  Bean Validation and the annotation          *
  *                  @ReportAsSingleViolation.                   *
  ****************************************************************
  * PROBLEM DESCRIPTION: Using @ReportAsSingleViolation causes   *
  *                      multiple errors to be reported.         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Take the following example:
  @NotNull
  @Size(min = 2, max = 10)
  ......
  @ReportAsSingleViolation
  public @interface MyInterface {
  Because @ReportAsSingleViolation is being used, only
  one violation should be reported for a violation such as null
  values.  However, the potential exists for multiple violations
  to occur when just one violation occurs.
  

Problem conclusion

• With this fix, code has been added to Bean Validation to
  ensure that the @ReportAsSingleViolation operations function
  as expected.
  
  The fix for this APAR is currently targeted for
  inclusion in Service Level (Fix Pack) 8.5.5.1 of WebSphere
  Application Server versions 8.5.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:

  PI59157

Fix information

• Fixed component name

  WEBS APP SERV N

• Fixed component ID

  5724H8800

Applicable component levels

• R850 PSY

     UP