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 e47610e Updates production by Jenkins
e47610e is described below
commit e47610e2ddf432ad9a309cca6cdfc2a913ea6c70
Author: jenkins <bui...@apache.org>
AuthorDate: Wed Nov 22 08:37:25 2017 +0000
Updates production by Jenkins
---
...onversion-error-field-validator-annotation.html | 10 +++-----
content/core-developers/type-conversion.html | 28 +++++++++++++++++++++-
content/security/index.html | 2 +-
3 files changed, 31 insertions(+), 9 deletions(-)
diff --git
a/content/core-developers/conversion-error-field-validator-annotation.html
b/content/core-developers/conversion-error-field-validator-annotation.html
index af5ea3c..50c2c5c 100644
--- a/content/core-developers/conversion-error-field-validator-annotation.html
+++ b/content/core-developers/conversion-error-field-validator-annotation.html
@@ -128,14 +128,12 @@
<a class="edit-on-gh"
href="https://github.com/apache/struts-site/edit/master/source/core-developers/conversion-error-field-validator-annotation.md";
title="Edit this page on GitHub">Edit on GitHub</a>
<h1
id="conversionerrorfieldvalidator-annotation">ConversionErrorFieldValidator
Annotation</h1>
-<p> This validator checks if there are any conversion errors for a field and
applies them if they exist.
- See <a
href="https://struts.apache.org/docs/type-conversion.html#TypeConversion-TypeConversionErrorHandling";>Type
Conversion Error Handling</a> for details.
-</p>
+<p>This validator checks if there are any conversion errors for a field and
applies them if they exist.
+See <a href="type-conversion.html#type-conversion-error-handling">Type
Conversion Error Handling</a> for details.</p>
<h2 id="usage">Usage</h2>
-<p> <p>The ConversionErrorFieldValidator annotation must be applied at method
level.</p>
-</p>
+<p>The <code class="highlighter-rouge">ConversionErrorFieldValidator</code>
annotation must be applied at method level.</p>
<h2 id="parameters">Parameters</h2>
@@ -188,11 +186,9 @@
<h2 id="examples">Examples</h2>
<div class="highlighter-rouge"><pre class="highlight"><code> <span
class="nd">@ConversionErrorFieldValidator</span><span class="o">(</span><span
class="n">message</span> <span class="o">=</span> <span class="s">"Default
message"</span><span class="o">,</span> <span class="n">key</span> <span
class="o">=</span> <span class="s">"i18n.key"</span><span class="o">,</span>
<span class="n">shortCircuit</span> <span class="o">=</span> <span
class="kc">true</span><span class="o">)</span>
-
</code></pre>
</div>
-
</section>
</article>
diff --git a/content/core-developers/type-conversion.html
b/content/core-developers/type-conversion.html
index d22b98e..27839ec 100644
--- a/content/core-developers/type-conversion.html
+++ b/content/core-developers/type-conversion.html
@@ -126,7 +126,33 @@
<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/type-conversion.md";
title="Edit this page on GitHub">Edit on GitHub</a>
- <h1 id="type-conversion">Type Conversion</h1>
+ <h1 class="no_toc" id="type-conversion">Type Conversion</h1>
+
+<ul id="markdown-toc">
+ <li><a href="#built-in-type-conversion-support"
id="markdown-toc-built-in-type-conversion-support">Built in Type Conversion
Support</a></li>
+ <li><a href="#relationship-to-parameter-names"
id="markdown-toc-relationship-to-parameter-names">Relationship to Parameter
Names</a></li>
+ <li><a href="#creating-a-type-converter"
id="markdown-toc-creating-a-type-converter">Creating a Type Converter</a></li>
+ <li><a href="#applying-a-type-converter-to-an-action"
id="markdown-toc-applying-a-type-converter-to-an-action">Applying a Type
Converter to an Action</a></li>
+ <li><a href="#applying-a-type-converter-to-a-bean-or-model"
id="markdown-toc-applying-a-type-converter-to-a-bean-or-model">Applying a Type
Converter to a bean or model</a></li>
+ <li><a href="#applying-a-type-converter-for-an-application"
id="markdown-toc-applying-a-type-converter-for-an-application">Applying a Type
Converter for an application</a></li>
+ <li><a href="#a-simple-example" id="markdown-toc-a-simple-example">A Simple
Example</a></li>
+ <li><a href="#advanced-type-conversion"
id="markdown-toc-advanced-type-conversion">Advanced Type Conversion</a> <ul>
+ <li><a href="#null-property-handling"
id="markdown-toc-null-property-handling">Null Property Handling</a></li>
+ </ul>
+ </li>
+ <li><a href="#collection-and-map-support"
id="markdown-toc-collection-and-map-support">Collection and Map Support</a>
<ul>
+ <li><a href="#indexing-a-collection-by-a-property-of-that-collection"
id="markdown-toc-indexing-a-collection-by-a-property-of-that-collection">Indexing
a collection by a property of that collection</a></li>
+ <li><a href="#an-advanced-example-for-indexed-lists-and-maps"
id="markdown-toc-an-advanced-example-for-indexed-lists-and-maps">An advanced
example for indexed Lists and Maps</a></li>
+ </ul>
+ </li>
+ <li><a href="#type-conversion-error-handling"
id="markdown-toc-type-conversion-error-handling">Type Conversion Error
Handling</a></li>
+ <li><a href="#common-problems" id="markdown-toc-common-problems">Common
Problems</a> <ul>
+ <li><a href="#null-and-blank-values"
id="markdown-toc-null-and-blank-values">Null and Blank Values</a></li>
+ <li><a href="#interfaces"
id="markdown-toc-interfaces">Interfaces</a></li>
+ <li><a href="#generics-and-erasure"
id="markdown-toc-generics-and-erasure">Generics and Erasure</a></li>
+ </ul>
+ </li>
+</ul>
<p>Routine type conversion in the framework is transparent. Generally, all you
need to do is ensure that HTML inputs have
names that can be used in <a href="ognl.html">OGNL</a> expressions. (HTML
inputs are form elements and other GET/POST parameters.)</p>
diff --git a/content/security/index.html b/content/security/index.html
index 72da646..b3d95dc 100644
--- a/content/security/index.html
+++ b/content/security/index.html
@@ -156,7 +156,7 @@
<h3 id="restrict-access-to-the-config-browser-plugin">Restrict access to the
Config Browser Plugin</h3>
-<p><a href="https://struts.apache.org/docs/config-browser-plugin.html";>Config
Browser Plugin</a> exposes internal configuration and should be used only
during development phase. If you must use it on production site, we strictly
recommend restricting access to it - you can use Basic Authentication or any
other security mechanism (e.g. <a href="https://shiro.apache.org/";>Apache
Shiro</a>)</p>
+<p><a href="../plugins/config-browser/">Config Browser Plugin</a> exposes
internal configuration and should be used only during development phase. If you
must use it on production site, we strictly recommend restricting access to it
- you can use Basic Authentication or any other security mechanism (e.g. <a
href="https://shiro.apache.org/";>Apache Shiro</a>)</p>
<h3 id="dont-mix-different-access-levels-in-the-same-namespace">Don’t mix
different access levels in the same namespace</h3>
--
To stop receiving notification emails like this one, please contact
['"commits@struts.apache.org" <commits@struts.apache.org>'].
