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 b48c8c79b Updates stage by Jenkins
b48c8c79b is described below

commit b48c8c79ba8e501245e5196616d077cfa9da10e9
Author: jenkins <bui...@apache.org>
AuthorDate: Wed Oct 19 13:54:33 2022 +0000

    Updates stage by Jenkins
---
 content/core-developers/result-types.html | 16 +++++++++++++---
 1 file changed, 13 insertions(+), 3 deletions(-)

diff --git a/content/core-developers/result-types.html 
b/content/core-developers/result-types.html
index 123754168..2f9dce3f4 100644
--- a/content/core-developers/result-types.html
+++ b/content/core-developers/result-types.html
@@ -129,7 +129,17 @@
   <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/result-types.md";
 title="Edit this page on GitHub">Edit on GitHub</a>
-    <h1 id="result-types">Result Types</h1>
+    <h1 class="no_toc" id="result-types">Result Types</h1>
+
+<ul id="markdown-toc">
+  <li><a href="#predefined-result-types" 
id="markdown-toc-predefined-result-types">Predefined Result Types</a></li>
+  <li><a href="#how-to-use-results" id="markdown-toc-how-to-use-results">How 
to use results</a></li>
+  <li><a href="#default-result-type" 
id="markdown-toc-default-result-type">Default result type</a></li>
+  <li><a href="#default-result-name" 
id="markdown-toc-default-result-name">Default result name</a></li>
+  <li><a href="#default-parameters" 
id="markdown-toc-default-parameters">Default parameters</a></li>
+  <li><a href="#registering-result-types" 
id="markdown-toc-registering-result-types">Registering result types</a></li>
+  <li><a href="#extending" id="markdown-toc-extending">Extending</a></li>
+</ul>
 
 <p>Most use cases can be divided into two phases. First, we need to change or 
query the application’s state, and then we need 
 to present an updated view of the application. The Action class manages the 
application’s state, and the Result Type 
@@ -241,7 +251,7 @@ specify the <code class="language-plaintext 
highlighter-rouge">type</code> attri
 <div class="language-xml highlighter-rouge"><div class="highlight"><pre 
class="highlight"><code><span 
class="nt">&lt;result&gt;</span>/WEB-INF/index.jsp<span 
class="nt">&lt;/result&gt;</span>
 </code></pre></div></div>
 
-<h2 id="default-parameters">Default Parameters</h2>
+<h2 id="default-parameters">Default parameters</h2>
 
 <p>To minimize configuration, Results can be configured with a single value, 
which will be converted into a parameter, 
 and each Result can specify which parameter this value should be set as. For 
example, here is a result defined in XML 
@@ -261,7 +271,7 @@ that uses a default parameter:</p>
 a significant amount of configuration. It also follows that if you have 
specified the default parameter, you don’t need 
 to set the same parameter as a specifically-named parameter.</p>
 
-<h2 id="registering-result-types">Registering Result Types</h2>
+<h2 id="registering-result-types">Registering result types</h2>
 
 <p>All Result Types are plugged in via the <a 
href="result-configuration">Result Configuration</a>.</p>
 

Reply via email to