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 cbfce90  Automatic Site Publish by Buildbot
cbfce90 is described below

commit cbfce90c0a554c9da82cd8a5fefa3ecc7bd6c512
Author: buildbot <us...@infra.apache.org>
AuthorDate: Thu Dec 17 09:40:54 2020 +0000

    Automatic Site Publish by Buildbot
---
 output/core-developers/default-properties.html | 4 ----
 output/tag-developers/alt-syntax.html          | 5 +++++
 2 files changed, 5 insertions(+), 4 deletions(-)

diff --git a/output/core-developers/default-properties.html 
b/output/core-developers/default-properties.html
index ecf0b38..0b3762f 100644
--- a/output/core-developers/default-properties.html
+++ b/output/core-developers/default-properties.html
@@ -267,10 +267,6 @@ struts.mapper.action.prefix.enabled = false
 ### Blocks access to actions in other namespace than current with action: 
prefix
 struts.mapper.action.prefix.crossNamespaces = false
 
-### use alternative syntax that requires %{} in most places
-### to evaluate expressions for String attributes for tags
-struts.tag.altSyntax=true
-
 ### when set to true, Struts will act much more friendly for developers. This
 ### includes:
 ### - struts.i18n.reload = true
diff --git a/output/tag-developers/alt-syntax.html 
b/output/tag-developers/alt-syntax.html
index ab70be4..0e748ca 100644
--- a/output/tag-developers/alt-syntax.html
+++ b/output/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>
 

Reply via email to