This is an automated email from the ASF dual-hosted git repository.

asf-gitbox-commits pushed a commit to branch asf-staging
in repository https://gitbox.apache.org/repos/asf/struts-site.git


The following commit(s) were added to refs/heads/asf-staging by this push:
     new 777e15e9e Updates stage by Jenkins
777e15e9e is described below

commit 777e15e9e3edfbf0a66cd32a6d3f0dfffcbe1457
Author: jenkins <[email protected]>
AuthorDate: Mon Sep 14 08:49:30 2026 +0000

    Updates stage by Jenkins
---
 content/core-developers/client-side-validation.html | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/content/core-developers/client-side-validation.html 
b/content/core-developers/client-side-validation.html
index c1a950632..869ab0ee4 100644
--- a/content/core-developers/client-side-validation.html
+++ b/content/core-developers/client-side-validation.html
@@ -281,7 +281,7 @@ an <code class="language-plaintext 
highlighter-rouge">int</code> or <code class=
     <tr>
       <td><code class="language-plaintext 
highlighter-rouge">visitor</code></td>
       <td>—</td>
-      <td>nothing for the visitor itself; the visited object’s own validators 
apply to its nested fields (<code class="language-plaintext 
highlighter-rouge">user.name</code>) exactly as if they were declared on the 
action</td>
+      <td>nothing for the visitor itself; the visited object’s own validators 
apply to its nested fields (<code class="language-plaintext 
highlighter-rouge">user.name</code>) exactly as if they were declared on the 
action, and their messages resolve as during validation — the visited class’s 
bundle first, then the action’s, with <code class="language-plaintext 
highlighter-rouge">${...}</code> read from the visited object when it 
exists</td>
     </tr>
     <tr>
       <td>any validator carrying a message</td>

Reply via email to