This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/struts-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 748c3a1 Automatic Site Publish by Buildbot
748c3a1 is described below
commit 748c3a18237019cb24964ee10728cdb2c997ab50
Author: buildbot <us...@infra.apache.org>
AuthorDate: Wed Jan 20 07:46:26 2021 +0000
Automatic Site Publish by Buildbot
---
output/core-developers/default-properties.html | 8 ++-
.../pure-java-script-client-side-validation.html | 78 ++++++++++------------
output/tag-developers/css-xhtml-theme.html | 2 +-
output/tag-developers/simple-theme.html | 2 +-
output/tag-developers/xhtml-theme.html | 2 +-
5 files changed, 45 insertions(+), 47 deletions(-)
diff --git a/output/core-developers/default-properties.html
b/output/core-developers/default-properties.html
index 4b0d31a..a004ecb 100644
--- a/output/core-developers/default-properties.html
+++ b/output/core-developers/default-properties.html
@@ -228,11 +228,15 @@ struts.multipart.maxSize=2097152
### prior to a comma e.g. struts.action.extension=, or
struts.action.extension=x,y,z,,
struts.action.extension=action,,
-### Used by FilterDispatcher
+### Used by Dispatcher
### If true then Struts serves static content from inside its jar.
-### If false then the static content must be available at
<context_path>/struts
+### If false then the static content must be available at
<context_path>/static
struts.serve.static=true
+### A path from which a static content is served, it must start with "/"
+### and it cannot end with "/"
+struts.ui.staticContentPath=/static
+
### Used by FilterDispatcher
### This is good for development where one wants changes to the static content
be
### fetch on each request.
diff --git
a/output/core-developers/pure-java-script-client-side-validation.html
b/output/core-developers/pure-java-script-client-side-validation.html
index e10d5e6..e8a482b 100644
--- a/output/core-developers/pure-java-script-client-side-validation.html
+++ b/output/core-developers/pure-java-script-client-side-validation.html
@@ -129,62 +129,56 @@
<section class="col-md-12">
<a href="index.html" title="back to Core Developers Guide"><< back to Core
Developers Guide</a>
<a class="edit-on-gh"
href="https://github.com/apache/struts-site/edit/master/source/core-developers/pure-java-script-client-side-validation.md";
title="Edit this page on GitHub">Edit on GitHub</a>
- <h1 id="pure-javascript-client-side-validation">Pure JavaScript Client
Side Validation</h1>
+ <h1 class="no_toc" id="pure-javascript-client-side-validation">Pure
JavaScript Client Side Validation</h1>
-<p>Pure JavaScript client side validation is the simplest but least
feature-rich type of <a href="client-side-validation.html">Client Side
Validation</a>.
-This type of validation uses 100% client-side JavaScript code to try to
validate the values entered by the user.
-Because the validation logic is actually repeated in the JavaScript code, it
is important to understand that
-some values will be considered acceptable by the JavaScript code but will be
marked as unacceptable by the server-side <a
href="validation.html">Validation</a>.</p>
-
-<p>Only the following validators are supported:
-* required validator
-* requiredstring validator
-* stringlength validator
-* regex validator
-* email validator
-* url validator
-* int validator
-* double validator
-</p>
+<ul id="markdown-toc">
+ <li><a href="#description" id="markdown-toc-description">Description</a></li>
+ <li><a href="#error-reporting" id="markdown-toc-error-reporting">Error
reporting</a></li>
+ <li><a href="#additional-validator-support"
id="markdown-toc-additional-validator-support">Additional Validator
Support</a></li>
+</ul>
-<blockquote>
+<h2 id="description">Description</h2>
-</blockquote>
+<p>Pure JavaScript client side validation is the simplest but least
feature-rich type of <a href="client-side-validation">Client Side
Validation</a>.
+This type of validation uses 100% client-side JavaScript code to try to
validate the values entered by the user.
+Because the validation logic is actually repeated in the JavaScript code, it
is important to understand that
+some values will be considered acceptable by the JavaScript code but will be
marked as unacceptable by the server-side <a
href="validation">Validation</a>.</p>
-<blockquote>
+<p>Only the following validators are supported:</p>
-</blockquote>
+<ul>
+ <li>required validator</li>
+ <li>requiredstring validator</li>
+ <li>stringlength validator</li>
+ <li>regex validator</li>
+ <li>email validator</li>
+ <li>url validator</li>
+ <li>int validator</li>
+ <li>double validator</li>
+</ul>
<blockquote>
<p>JavaScript client validation is not available for visitor validations.</p>
</blockquote>
-<blockquote>
-
-</blockquote>
-
-<p><strong>Error reporting</strong></p>
+<h2 id="error-reporting">Error reporting</h2>
-<p>Because client side validation does not talk to the server, the theme
(<em>xhtml theme</em> or <em>css_xhtml theme</em> ) is responsible for
properly manipulating the HTML DOM to display the error message inline. The
JavaScript that is responsible for doing this logic is <code
class="highlighter-rouge">validation.js</code> and can be found in each
theme.</p>
+<p>Because client side validation does not talk to the server, the theme
(<em>xhtml theme</em> or <em>css_xhtml theme</em> ) is responsible
+for properly manipulating the HTML DOM to display the error message inline.
The JavaScript that is responsible for doing
+this logic is <code class="highlighter-rouge">validation.js</code> and can be
found in each theme.</p>
-<table>
- <tbody>
- <tr>
- <td>Errors are reported using the default validation message, not the
internationalized version that the server-side might be aware of. This is a
known issue. You may want to try the <a
href="ajax-client-side-validation.html">AJAX Client Side Validation</a> for
messages that are fully internationalized.</td>
- </tr>
- </tbody>
-</table>
-
-<table>
- <tbody>
- <tr>
- </tr>
- </tbody>
-</table>
+<blockquote>
+ <p>Errors are reported using the default validation message, not the
internationalized version that the server-side might
+be aware of. This is a known issue. You may want to try the <a
href="ajax-client-side-validation">AJAX Client Side Validation</a>
+for messages that are fully internationalized.</p>
+</blockquote>
-<p><strong>Additional Validator Support</strong></p>
+<h2 id="additional-validator-support">Additional Validator Support</h2>
-<p>If you wish to add additional validator support beyond those listed, you
may override the <em>xhtml theme</em> teamplte <code
class="highlighter-rouge">form-close-validate.ftl</code>. This file contains
the JavaScript that tries to validate each user-entered value from within the
browswer. The <em>css_xhtml theme</em> extends the <em>xhtml theme</em> and
therefore doesn’t have it’s own form-close-validate.ftl template.</p>
+<p>If you wish to add additional validator support beyond those listed, you
may override the <em>xhtml theme</em> template
+<code class="highlighter-rouge">form-close-validate.ftl</code>. This file
contains the JavaScript that tries to validate each user-entered value from
within
+the browser. The <em>css_xhtml theme</em> extends the <em>xhtml theme</em>
and therefore doesn’t have its own <code
class="highlighter-rouge">form-close-validate.ftl</code>
+template.</p>
</section>
</article>
diff --git a/output/tag-developers/css-xhtml-theme.html
b/output/tag-developers/css-xhtml-theme.html
index 6a2aad2..eb9f02b 100644
--- a/output/tag-developers/css-xhtml-theme.html
+++ b/output/tag-developers/css-xhtml-theme.html
@@ -328,7 +328,7 @@ to provide the layout. The contents of
<strong>head.ftl</strong> are:</p>
* under the License.
*/
-->
-<link <#include "/${parameters.templateDir}/simple/nonce.ftl" />
rel="stylesheet" href="<@s.url value='/struts/css_xhtml/styles.css'
includeParams='none' encode='false' />" type="text/css" />
+<link <#include "/${parameters.templateDir}/simple/nonce.ftl" />
rel="stylesheet" href="<@s.url
value='${parameters.staticContentPath}/css_xhtml/styles.css'
includeParams='none' encode='false' />" type="text/css" />
<#include "/${parameters.templateDir}/simple/head.ftl"
/></code></pre></figure>
<p>The head includes a style sheet. The contents of
<strong>styles.css</strong> are:</p>
diff --git a/output/tag-developers/simple-theme.html
b/output/tag-developers/simple-theme.html
index 2b2b1f8..78d1129 100644
--- a/output/tag-developers/simple-theme.html
+++ b/output/tag-developers/simple-theme.html
@@ -181,7 +181,7 @@ Ajax/Dojo support so that tags can import Dojo widgets
easily.</p>
* under the License.
*/
-->
-<script src="${base}/struts/utils.js" type="text/javascript" <#include
"/${parameters.templateDir}/simple/nonce.ftl" />
></script></code></pre></figure>
+<script src="${base}${parameters.staticContentPath}/utils.js"
type="text/javascript" <#include
"/${parameters.templateDir}/simple/nonce.ftl" />
></script></code></pre></figure>
</section>
diff --git a/output/tag-developers/xhtml-theme.html
b/output/tag-developers/xhtml-theme.html
index 50499ca..772ff56 100644
--- a/output/tag-developers/xhtml-theme.html
+++ b/output/tag-developers/xhtml-theme.html
@@ -392,7 +392,7 @@ render the form elements.</p>
* under the License.
*/
-->
-<link rel="stylesheet" href="<@s.url value='/struts/xhtml/styles.css'
includeParams='none' encode='false'/>" type="text/css" <#include
"/${parameters.templateDir}/simple/nonce.ftl" /> />
+<link rel="stylesheet" href="<@s.url
value='${parameters.staticContentPath}/xhtml/styles.css' includeParams='none'
encode='false'/>" type="text/css" <#include
"/${parameters.templateDir}/simple/nonce.ftl" /> />
<#include "/${parameters.templateDir}/simple/head.ftl"
/></code></pre></figure>
<p>The head template imports a style sheet. The contents of
<strong>styles.css</strong> are:</p>
