Bug 1307263

Summary:	[GSS](6.4.z) HV-665 - Consider concerned constraint in identity of constraint violations
Product:	[JBoss] JBoss Enterprise Application Platform 6	Reporter:	Brad Maxwell <bmaxwell>
Component:	Hibernate	Assignee:	Gail Badner <gbadner>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Martin Simka <msimka>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	6.4.6	CC:	bbaranow, gbadner, jbilek, jtruhlar, msimka, rnetuka, rpelisse, smarlow, tom.ross
Target Milestone:	CR1
Target Release:	EAP 6.4.9
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-01-17 12:54:57 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1305442, 1307264, 1324262

Description Brad Maxwell 2016-02-13 19:42:41 UTC

Currently the concerned constraint is not considered when determining the identity of ConstraintViolationImpl (equals() and hashCode()). This causes only one violation to be contained in the set returned by Validator#validate() when validating e.g. the following property:

@Size(min=2, message="must be 2 at least")
@DecimalMin(value="2", message="must be 2 at least")
String name = "1";

Comment 1 Brad Maxwell 2016-02-13 19:43:46 UTC

https://hibernate.atlassian.net/browse/HV-665

Comment 6 Jiří Bílek 2016-06-28 13:10:20 UTC

Verified with EAP 6.4.9.CP.CR2

Comment 7 Petr Penicka 2017-01-17 12:54:57 UTC

Retroactively bulk-closing issues from released EAP 6.4 cummulative patches.