Bug 1295679

Summary: better error messages for beanvalidation validation failures.
Product: [oVirt] ovirt-engine Reporter: Martin Mucha <mmucha>
Component: BLL.InfraAssignee: Oved Ourfali <oourfali>
Status: CLOSED DUPLICATE QA Contact: Pavel Stehlik <pstehlik>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: futureCC: alkaplan, bugs, mmucha
Target Milestone: ---Flags: rule-engine: planning_ack?
rule-engine: devel_ack?
rule-engine: testing_ack?
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-05 09:47:04 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:
Embargoed:

Description Martin Mucha 2016-01-05 08:38:25 UTC 
Description of problem:
currently, if big transfer object (*Parameters) is validated, only the message of failure is rendered to the user. That is description of failing field. However if given transfer object forms along aggregations a deep tree, it would be better if better identification of failing field is provided. Imagine *Parameters class, which aggregates 20 another bean in collection; it'd be better if failing bean is identified.

Each ConstraintViolation instance has propertyPath exactly identifying record containing failing field. We can somehow use this information and present it to the user.
Comment 1 Yaniv Kaul 2016-01-05 09:05:36 UTC 
Dup of bug 1295678 ?
Comment 2 Martin Mucha 2016-01-05 09:47:04 UTC 
yes. (bugzilla bug when creating new bug)

*** This bug has been marked as a duplicate of bug 1295678 ***