[struts-site] branch asf-staging updated: Updates stage by Jenkins

[git-site-role]

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

commit 99102ea87c6050a4876267a7cc62333de83caf77
Author: jenkins <bui...@apache.org>
AuthorDate: Thu May 25 07:58:02 2023 +0000

    Updates stage by Jenkins
---
 content/tag-developers/ognl.html | 20 ++++++++++++--------
 1 file changed, 12 insertions(+), 8 deletions(-)

diff --git a/content/tag-developers/ognl.html b/content/tag-developers/ognl.html
index bd71b661d..27f333320 100644
--- a/content/tag-developers/ognl.html
+++ b/content/tag-developers/ognl.html
@@ -134,6 +134,8 @@
     <h1 class="no_toc" id="ognl">OGNL</h1>
 
 <ul id="markdown-toc">
+  <li><a href="#context" id="markdown-toc-context">Context</a></li>
+  <li><a href="#referencing-an-action-property" 
id="markdown-toc-referencing-an-action-property">Referencing an Action 
property</a></li>
   <li><a href="#collections-maps-lists-sets" 
id="markdown-toc-collections-maps-lists-sets">Collections (Maps, Lists, 
Sets)</a></li>
 </ul>
 
@@ -146,10 +148,12 @@ a Map (usually referred as a context map or context). 
OGNL has a notion of there
 the context. In expression, the properties of the root object can be 
referenced without any special “marker” notion. 
 References to other objects are marked with a pound sign (<code 
class="language-plaintext highlighter-rouge">#</code>).</p>
 
-<p>The framework sets the OGNL context to be our ActionContext, and the value 
stack to be the OGNL root object. 
-(The value stack is a set of several objects, but to OGNL it appears to be a 
single object.) Along with the value stack, 
-the framework places other objects in the ActionContext, including Maps 
representing the application, session, 
-and request contexts. These objects coexist in the ActionContext, alongside 
the value stack (our OGNL root).</p>
+<h2 id="context">Context</h2>
+
+<p>The framework sets the OGNL context to be our <code 
class="language-plaintext highlighter-rouge">ActionContext</code>, and the 
<code class="language-plaintext highlighter-rouge">ValueStack</code> to be the 
OGNL root object. 
+(The <code class="language-plaintext highlighter-rouge">ValueStack</code> is a 
set of several objects, but to OGNL it appears to be a single object). Along 
with the value stack, 
+the framework places other objects in the <code class="language-plaintext 
highlighter-rouge">ActionContext</code>, including maps representing the 
application, session, 
+and request contexts. These objects coexist in the <code 
class="language-plaintext highlighter-rouge">ActionContext</code>, alongside 
the value stack (our OGNL root).</p>
 
 <div class="language-plaintext highlighter-rouge"><div class="highlight"><pre 
class="highlight"><code>context map---|
               |--application
@@ -168,11 +172,11 @@ and request contexts. These objects coexist in the 
ActionContext, alongside the
               |
 </code></pre></div></div>
 
-<p>The Action instance is always pushed onto the value stack. Because the 
Action is on the stack, and the stack is 
-the OGNL root, references to Action properties can omit the <code 
class="language-plaintext highlighter-rouge">#</code> marker. But, to access 
other objects in the ActionContext, 
-we must use the <code class="language-plaintext highlighter-rouge">#</code> 
notation so OGNL knows not to look in the root object, but for some other 
object in the ActionContext.</p>
+<h2 id="referencing-an-action-property">Referencing an Action property</h2>
 
-<p><strong>Referencing an Action property</strong></p>
+<p>The Action instance is always pushed onto the value stack. Because the 
Action is on the stack, and the stack is
+the OGNL root, references to Action properties can omit the <code 
class="language-plaintext highlighter-rouge">#</code> marker. But, to access 
other objects in the ActionContext,
+we must use the <code class="language-plaintext highlighter-rouge">#</code> 
notation so OGNL knows not to look in the root object, but for some other 
object in the ActionContext.</p>
 
 <div class="language-jsp highlighter-rouge"><div class="highlight"><pre 
class="highlight"><code><span class="nt">&lt;s:property </span><span 
class="na">value=</span><span class="s">"postalCode"</span><span 
class="nt">/&gt;</span>
 </code></pre></div></div>