This is an automated email from the ASF dual-hosted git repository.
git-site-role 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 c164a68da Updates stage by Jenkins
c164a68da is described below
commit c164a68da8d48c48a26b11aedc1609b106e9d90e
Author: jenkins <[email protected]>
AuthorDate: Fri Oct 17 10:13:57 2025 +0000
Updates stage by Jenkins
---
content/core-developers/action-configuration.html | 4 ---
content/core-developers/validation.html | 39 ++--------------------
.../getting-started/form-validation-using-xml.html | 4 ---
3 files changed, 3 insertions(+), 44 deletions(-)
diff --git a/content/core-developers/action-configuration.html
b/content/core-developers/action-configuration.html
index 615b9d7da..83d4d30bd 100644
--- a/content/core-developers/action-configuration.html
+++ b/content/core-developers/action-configuration.html
@@ -229,10 +229,6 @@ to specifically allow slashes in your action names via a
constant in the <code c
<p>See <a href="https://issues.apache.org/jira/browse/WW-1383";>JIRA Issue
WW-1383</a> for discussion as there are side effects
to setting this property to <code class="language-plaintext
highlighter-rouge">true</code>.</p>
-<blockquote>
- <p><strong>Note:</strong> When using slashes in action names, validation
file naming requires special attention. Slashes in action aliases are replaced
with hyphens in validation file names. See <a
href="validation#validation-files-for-actions-with-slashes">Validation Files
for Actions with Slashes</a> for detailed information.</p>
-</blockquote>
-
<p><strong>Action Names with Dots and Dashes</strong></p>
<p>Although action naming is pretty flexible, one should pay attention when
using dots (eg. create.user) and/or dashes
diff --git a/content/core-developers/validation.html
b/content/core-developers/validation.html
index 3d818a276..82d6a248e 100644
--- a/content/core-developers/validation.html
+++ b/content/core-developers/validation.html
@@ -162,10 +162,7 @@
<li><a href="#turning-on-validation"
id="markdown-toc-turning-on-validation">Turning on Validation</a></li>
<li><a href="#validator-scopes" id="markdown-toc-validator-scopes">Validator
Scopes</a></li>
<li><a href="#notes" id="markdown-toc-notes">Notes</a></li>
- <li><a href="#defining-validation-rules"
id="markdown-toc-defining-validation-rules">Defining Validation Rules</a>
<ul>
- <li><a href="#validation-files-for-actions-with-slashes"
id="markdown-toc-validation-files-for-actions-with-slashes">Validation Files
for Actions with Slashes</a></li>
- </ul>
- </li>
+ <li><a href="#defining-validation-rules"
id="markdown-toc-defining-validation-rules">Defining Validation Rules</a></li>
<li><a href="#localizing-and-parameterizing-messages"
id="markdown-toc-localizing-and-parameterizing-messages">Localizing and
Parameterizing Messages</a> <ul>
<li><a href="#customizing-validation-messages"
id="markdown-toc-customizing-validation-messages">Customizing validation
messages</a></li>
</ul>
@@ -184,7 +181,7 @@ combined with XML and annotation-driven validation.</p>
<p>Validation also depends on both the <code class="language-plaintext
highlighter-rouge">validation</code> and <code class="language-plaintext
highlighter-rouge">workflow</code> interceptors (both are included in the
default interceptor
stack). The <code class="language-plaintext
highlighter-rouge">validation</code> interceptor does the validation itself and
creates a list of field-specific errors.
The <code class="language-plaintext highlighter-rouge">workflow</code>
interceptor checks for the presence of validation errors: if any are found, it
returns the “input” result
-(by default), taking the user back to the form which contained the validation
errors. See <a href="default-workflow-interceptor">Default Workflow
Interceptor</a> for details on method-specific validation and workflow
behavior.</p>
+(by default), taking the user back to the form which contained the validation
errors.</p>
<p>If we’re using the default settings <em>and</em> our action does not have
an “input” result defined <em>and</em> there are validation
(or, incidentally, type conversion) errors, we’ll get an error message back
telling us there’s no “input” result defined
@@ -316,36 +313,6 @@ XWork searches up the inheritance tree of the action to
find default
validations for parent classes of the Action and interfaces implemented</li>
</ol>
-<p><strong>Note on “Action Alias”:</strong> In this context, “action alias”
refers to the action name specified in the <code class="language-plaintext
highlighter-rouge">name</code> attribute of the <code class="language-plaintext
highlighter-rouge"><action></code> element in your Struts configuration
(e.g., <code class="language-plaintext highlighter-rouge">struts.xml</code>).
For example, if you have <code class="language-plaintext
highlighter-rouge"><action name="editUser" cl [...]
-
-<h3 id="validation-files-for-actions-with-slashes">Validation Files for
Actions with Slashes</h3>
-
-<p>When using action names with slashes (enabled via <code
class="language-plaintext
highlighter-rouge">struts.enable.SlashesInActionNames</code>), the validation
file naming follows a special rule: <strong>slashes in the action alias are
replaced with hyphens</strong>.</p>
-
-<p><strong>Pattern:</strong> <code class="language-plaintext
highlighter-rouge">ClassName-{action-alias-with-slashes-replaced-by-hyphens}-validation.xml</code></p>
-
-<p><strong>Example:</strong></p>
-
-<p>For this action configuration:</p>
-<div class="language-xml highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="nt"><constant</span> <span
class="na">name=</span><span
class="s">"struts.enable.SlashesInActionNames"</span> <span
class="na">value=</span><span class="s">"true"</span><span
class="nt">/></span>
-
-<span class="nt"><action</span> <span class="na">name=</span><span
class="s">"a/b/myaction.validate"</span>
- <span class="na">class=</span><span class="s">"myPath.MyAction"</span>
- <span class="na">method=</span><span class="s">"create"</span><span
class="nt">></span>
- <span class="nt"><result</span> <span class="na">name=</span><span
class="s">"input"</span> <span class="na">type=</span><span
class="s">"tiles"</span><span class="nt">></span>mytiles<span
class="nt"></result></span>
-<span class="nt"></action></span>
-</code></pre></div></div>
-
-<p>The validation file should be named:</p>
-<ul>
- <li><strong>Action-specific alias validation:</strong> <code
class="language-plaintext
highlighter-rouge">MyAction-a-b-myaction.validate-validation.xml</code></li>
- <li><strong>General action validation:</strong> <code
class="language-plaintext highlighter-rouge">MyAction-validation.xml</code>
(applies to all aliases)</li>
-</ul>
-
-<p><strong>Location:</strong> Place validation files in <code
class="language-plaintext highlighter-rouge">src/main/resources/myPath/</code>
(following your package structure)</p>
-
-<p>This behavior is implemented in <code class="language-plaintext
highlighter-rouge">AnnotationActionValidatorManager</code> where <code
class="language-plaintext highlighter-rouge">context.replace('/', '-')</code>
converts the action alias for file resolution.</p>
-
<p>Here is an example for SimpleAction-validation.xml:</p>
<div class="language-xml highlighter-rouge"><div class="highlight"><pre
class="highlight"><code><span class="cp"><!DOCTYPE validators PUBLIC
"-//Apache Struts//XWork Validator 1.0.3//EN"
@@ -664,7 +631,7 @@ and Field validators for email2 field to not be validated
as well.</p>
<p><strong>Usefull Information:</strong>
More complicated validation should probably be done in the <code
class="language-plaintext highlighter-rouge">validate()</code> method on the
action itself (assuming the action
-implements <code class="language-plaintext
highlighter-rouge">Validatable</code> interface which <code
class="language-plaintext highlighter-rouge">ActionSupport</code> already
does). You can also use method-specific validation methods like <code
class="language-plaintext highlighter-rouge">validate{MethodName}()</code> or
<code class="language-plaintext
highlighter-rouge">validateDo{MethodName}()</code> - see <a
href="default-workflow-interceptor">Default Workflow Interceptor</a> for de
[...]
+implements <code class="language-plaintext
highlighter-rouge">Validatable</code> interface which <code
class="language-plaintext highlighter-rouge">ActionSupport</code> already
does).</p>
<p>A plain Validator (non FieldValidator) that gets short-circuited will
completely break out of the validation stack.
No other validators will be evaluated and plain validators takes precedence
over field validators meaning that they
diff --git a/content/getting-started/form-validation-using-xml.html
b/content/getting-started/form-validation-using-xml.html
index 272318880..06221a0c9 100644
--- a/content/getting-started/form-validation-using-xml.html
+++ b/content/getting-started/form-validation-using-xml.html
@@ -194,10 +194,6 @@ The information that can be edited is encapsulated in an
object of class Person.
The XML file that contains the validation rules must be named as
ActionClassName-validation.xml. In the example
application, the XML validation file is named EditAction-validation.xml (see
src/main/resources/org/apache/struts/edit/action).</p>
-<blockquote>
- <p><strong>Note:</strong> When using action names with slashes (enabled via
<code class="language-plaintext
highlighter-rouge">struts.enable.SlashesInActionNames</code>), validation file
naming follows a special rule where slashes are replaced with hyphens. See <a
href="../core-developers/validation#validation-files-for-actions-with-slashes">Validation
Files for Actions with Slashes</a> for detailed information.</p>
-</blockquote>
-
<p>Struts provides several different validators that you can use in the XML
validation file. See <a href="../core-developers/validation">Validation</a>
for a list of validators you can employ.</p>
