[
https://issues.apache.org/jira/browse/TOMEE-4647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Markus Jung updated TOMEE-4647:
-------------------------------
Description:
A method annotated with a {{@FooConstraint}} bean validation constraint fails
validation as expected, but the violation message does not show up on the
rendered page. The check runs through TomEE's BVal and OpenWebBeans
method-validation integration.
The constraint check itself works: the method call is intercepted and the
constraint is checked. The gap is in how the resulting violation message
reaches the rendered output. Somewhere between the BVal interceptor and the
Faces page, the message gets lost or is not passed through.
h2. Steps to reproduce / TCK reference
* Test class: {{MethodValidationIT}}
* Excluded in: {{runner-standalone/exclusions/faces.txt}} in the
apache/tomee-tck harness repo.
Run the Jakarta Faces standalone TCK runner with this test enabled. The test
calls a method that carries a {{@FooConstraint}} constraint and expects the
violation message on the rendered page. Remove the exclusion once fixed and
confirm the test passes.
was:
h2. Description
A method annotated with a {{@FooConstraint}} bean validation constraint fails
validation as expected, but the violation message does not show up on the
rendered page. The check runs through TomEE's BVal and OpenWebBeans
method-validation integration.
The constraint check itself works: the method call is intercepted and the
constraint is checked. The gap is in how the resulting violation message
reaches the rendered output. Somewhere between the BVal interceptor and the
Faces page, the message gets lost or is not passed through.
h2. Steps to reproduce / TCK reference
* Test class: {{MethodValidationIT}}
* Excluded in: {{runner-standalone/exclusions/faces.txt}} in the
apache/tomee-tck harness repo.
Run the Jakarta Faces standalone TCK runner with this test enabled. The test
calls a method that carries a {{@FooConstraint}} constraint and expects the
violation message on the rendered page. Remove the exclusion once fixed and
confirm the test passes.
> CDI method-level constraint violation message missing from rendered Faces page
> ------------------------------------------------------------------------------
>
> Key: TOMEE-4647
> URL: https://issues.apache.org/jira/browse/TOMEE-4647
> Project: TomEE
> Issue Type: Bug
> Reporter: Markus Jung
> Priority: Major
>
> A method annotated with a {{@FooConstraint}} bean validation constraint fails
> validation as expected, but the violation message does not show up on the
> rendered page. The check runs through TomEE's BVal and OpenWebBeans
> method-validation integration.
> The constraint check itself works: the method call is intercepted and the
> constraint is checked. The gap is in how the resulting violation message
> reaches the rendered output. Somewhere between the BVal interceptor and the
> Faces page, the message gets lost or is not passed through.
> h2. Steps to reproduce / TCK reference
> * Test class: {{MethodValidationIT}}
> * Excluded in: {{runner-standalone/exclusions/faces.txt}} in the
> apache/tomee-tck harness repo.
> Run the Jakarta Faces standalone TCK runner with this test enabled. The test
> calls a method that carries a {{@FooConstraint}} constraint and expects the
> violation message on the rendered page. Remove the exclusion once fixed and
> confirm the test passes.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
