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

commit 9adc5529b0b7a81ff103a580c40089e6867a5695
Author: jenkins <bui...@apache.org>
AuthorDate: Sat Dec 19 21:31:35 2020 +0000

    Updates stage by Jenkins
---
 .../accessing-application-session-request-objects.html               | 4 ++--
 content/tag-developers/alt-syntax.html                               | 5 +++++
 content/tag-developers/set-tag.html                                  | 4 ++--
 3 files changed, 9 insertions(+), 4 deletions(-)

diff --git 
a/content/core-developers/accessing-application-session-request-objects.html 
b/content/core-developers/accessing-application-session-request-objects.html
index d864d0e..21bf18c 100644
--- a/content/core-developers/accessing-application-session-request-objects.html
+++ b/content/core-developers/accessing-application-session-request-objects.html
@@ -183,7 +183,7 @@ doesn’t exist, it will search the request, session, and 
application scopes, in
 
 <p><strong>Accessing attributes in the Application, Session, Request, or Page 
scope from a JSP</strong></p>
 
-<pre><code class="language-jsp">Retrieve the attribute (property), with key 
myId, from the specified scope:
+<pre><code class="language-jsp">&lt;p&gt;Retrieve the attribute (property), 
with key myId, from the specified scope:&lt;/p&gt;
 
 &lt;s:property value="#application.myId" /&gt;
 
@@ -193,7 +193,7 @@ doesn’t exist, it will search the request, session, and 
application scopes, in
 
 &lt;s:property value="#attr.myId" /&gt;
 
-Reminder: attr is for Page scope attributes first, but will search the 
remaining scopes, in order, seeking a match.
+&lt;p&gt;Reminder: #attr is for Page scope attributes first, but will search 
the remaining scopes, in order, seeking a match.&lt;/p&gt;
 </code></pre>
 
   </section>
diff --git a/content/tag-developers/alt-syntax.html 
b/content/tag-developers/alt-syntax.html
index ab70be4..0e748ca 100644
--- a/content/tag-developers/alt-syntax.html
+++ b/content/tag-developers/alt-syntax.html
@@ -133,6 +133,11 @@
     
     <h1 id="alt-syntax">Alt Syntax</h1>
 
+<blockquote>
+  <p>Note: As from Struts 2.6 option to disable the AltSyntax has been removed 
and now using %{…} is the only way 
+to create an expression as stated below.</p>
+</blockquote>
+
 <p>The <em>altSyntax</em> is an option that can be defined in <code 
class="highlighter-rouge">struts.xml</code>. By default it is set to true and 
it is <strong>strongly</strong> 
 recommend you do not change that unless you are upgrading from WebWork 2.1.7 
or previous versions.</p>
 
diff --git a/content/tag-developers/set-tag.html 
b/content/tag-developers/set-tag.html
index 33cd79a..11d9502 100644
--- a/content/tag-developers/set-tag.html
+++ b/content/tag-developers/set-tag.html
@@ -150,13 +150,13 @@ the body evaluates is set as value for the scoped 
variable.</p>
   <li><code class="highlighter-rouge">application</code> - the value will be 
set in application scope according to servlet spec. using the name as its 
key</li>
   <li><code class="highlighter-rouge">session</code> - the value will be set 
in session scope according to servlet spec. using the name as key</li>
   <li><code class="highlighter-rouge">request</code> - the value will be set 
in request scope according to servlet spec. using the name as key</li>
-  <li><code class="highlighter-rouge">page</code> - the value will be set in 
page scope according to servlet spec. using the name as key</li>
+  <li><code class="highlighter-rouge">page</code> - the value will be set in 
page scope according to servlet spec. using the name as key (retrieve via 
#attr)</li>
   <li><code class="highlighter-rouge">action</code> - the value will be set in 
the page scope and Struts’ action context using the name as key</li>
 </ul>
 
 <blockquote>
   <p><strong>NOTE</strong>: If no scope is specified, it will default to <code 
class="highlighter-rouge">action</code> scope.  For the <code 
class="highlighter-rouge">set</code> tag <strong>specifically</strong>, this 
also
-places (sets) the generated value into the <code 
class="highlighter-rouge">page</code> scope as well.</p>
+places (sets) the generated value into the <code 
class="highlighter-rouge">page</code> scope as well (retrieve via #attr).</p>
 </blockquote>
 
 <p>Assigns a value to a variable in a specified scope</p>

Reply via email to