Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BVAL-690 Clarifying semantics of getLeafBean() for container-element … #237

Closed
wants to merge 1 commit into from

Conversation

gunnarmorling
Copy link
Contributor

…constraints;

Also expending the example to cover that case

https://hibernate.atlassian.net/browse/BVAL-690

----
//assuming an english locale, the interpolated message is returned
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These sections don't have changed at all, I just pulled the into actual source files to be sure they compile and are correct.

@@ -456,10 +456,10 @@ include::{validation-api-source-dir}javax/validation/ConstraintViolation.java[li
The [methodname]`getLeafBean()` method returns the following object:

* If a bean constraint, the bean instance the constraint is applied on.
* If a property constraint, the bean instance hosting the property the constraint is applied on.
* If a property constraint or a <<constraintdeclarationvalidationprocess-containerelementconstraints,container-element constraint>> hosted on a property, the bean instance hosting the property the constraint is applied on.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Same remark about the hyphen.

…constraints;

Also expending the example to cover that case
@gsmet
Copy link
Contributor

gsmet commented Jul 7, 2017

Rebased and merged, thanks!

@gsmet gsmet closed this Jul 7, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants