PI58523: When using jpa-2.1 with Bean Validation, XML constraints are not recognized.

Fixes are available

APAR status

Closed as program error.

Error description

When using bean validation, constraints can be defined using
annotations or XML. When using jpa-2.1, if an entity is
constrained using XML constraints, the entity is not
validated properly. This is caused by EclipseLink, the
jpa-2.1 provider, not detecting XML constraints when
optimizing validation.

Local fix

Problem summary

****************************************************************
* USERS AFFECTED:  All users of IBM WebSphere Application      *
*                  Server Liberty - Java Persistence API (JPA  *
*                  2.1) with Bean Validation                   *
****************************************************************
* PROBLEM DESCRIPTION: When using jpa-2.1 with Bean            *
*                      Validation, XML constraints are not     *
*                      recognized.                             *
****************************************************************
* RECOMMENDATION:                                              *
****************************************************************
When using bean validation, constraints can be defined using
annotations or XML. When using jpa-2.1, if an entity is
constrained using XML constraints, the entity is not validated
properly. This is caused by EclipseLink, the jpa-2.1 provider,
not detecting XML constraints when optimizing validation.

Problem conclusion

EclipseLink, the jpa-2.1 provider, was fixed and updated in
WebSphere Liberty to detect bean validation XML constraints when
optimizing validation.

The fix for this APAR is currently targeted for inclusion in fix
pack 16.0.0.2.  Please refer to the Recommended Updates page for
delivery information:
http://www.ibm.com/support/docview.wss?rs=180&uid=swg27004980

Temporary fix

When using bean validation with jpa-2.1, use annotation
constraints instead of XML constraints.

Comments

APAR Information

APAR number
PI58523
Reported component name
LIBERTY PROFILE
Reported component ID
5724J0814
Reported release
855
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2016-03-03
Closed date
2016-03-08
Last modified date
2016-06-13

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
LIBERTY PROFILE
Fixed component ID
5724J0814

Applicable component levels

R855 PSY
UP

[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSEQTP","label":"WebSphere Application Server"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"855","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
04 May 2022

Tips

PI58523: When using jpa-2.1 with Bean Validation, XML constraints are not recognized.

Fixes are available

Subscribe

APAR status

Closed as program error.

Error description

Local fix

Problem summary

Problem conclusion

Temporary fix

Comments

APAR Information

APAR number

Reported component name

Reported component ID

Reported release

Status

PE

HIPER

Special Attention

Submitted date

Closed date

Last modified date

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

Fixed component ID

Applicable component levels

R855 PSY

Document Information

Share your feedback

Need support?