struts-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From yasserzam...@apache.org
Subject [struts-site] branch master updated: Replaces ([a-z]\s)\n\n~~~~~~~\n([^\n]{1, 52})\n~~~~~~~\n with $1`$2`
Date Thu, 23 Nov 2017 17:01:55 GMT
This is an automated email from the ASF dual-hosted git repository.

yasserzamani pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/struts-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 1a2dadd  Replaces ([a-z]\s)\n\n~~~~~~~\n([^\n]{1,52})\n~~~~~~~\n with $1`$2`
1a2dadd is described below

commit 1a2dadd9bfcb12e2a7f9816eb023088481a800bb
Author: Yasser Zamani <yasserzamani@apache.org>
AuthorDate: Thu Nov 23 20:31:37 2017 +0330

    Replaces ([a-z]\s)\n\n~~~~~~~\n([^\n]{1,52})\n~~~~~~~\n with $1`$2`
---
 source/core-developers/basic-validation.md         |  7 +---
 source/core-developers/client-validation.md        |  7 +---
 .../configuration-provider-and-configuration.md    | 14 +------
 source/core-developers/file-upload.md              | 35 +++--------------
 source/core-developers/freemarker-support.md       | 26 ++-----------
 source/core-developers/glassfish-2-x.md            |  7 +---
 source/core-developers/jboss-5.md                  | 12 +-----
 source/core-developers/object-factory.md           |  7 +---
 .../core-developers/parent-package-annotation.md   |  7 +---
 .../pure-java-script-client-side-validation.md     |  7 +---
 source/core-developers/result-annotation.md        | 21 ++--------
 source/core-developers/sunone-7-0.md               | 21 ++--------
 source/core-developers/weblogic-6-1.md             | 14 +------
 source/core-developers/websphere.md                | 14 +------
 source/core-developers/zero-configuration.md       |  7 +---
 source/tag-developers/ajax-common-header.md        |  7 +---
 source/tag-developers/dojo-autocompleter-tag.md    |  7 +---
 source/tag-developers/form-tags.md                 | 26 ++-----------
 source/tag-developers/tag-syntax.md                | 45 +++-------------------
 19 files changed, 38 insertions(+), 253 deletions(-)

diff --git a/source/core-developers/basic-validation.md b/source/core-developers/basic-validation.md
index 6ab92ed..8bdc7ff 100644
--- a/source/core-developers/basic-validation.md
+++ b/source/core-developers/basic-validation.md
@@ -100,12 +100,7 @@ public class QuizAction extends ActionSupport {
 
 ## Step 3
 
-Create the validators\. The `validation.xml` format is either `<ActionClassName>-validation.xml`
or 
-
-~~~~~~~
-<ActionClassName>-<ActionAliasName>-validation.xml
-~~~~~~~
-\.
+Create the validators\. The `validation.xml` format is either `<ActionClassName>-validation.xml`
or `<ActionClassName>-<ActionAliasName>-validation.xml`\.
 
 {% comment %}start snippet id=quizValidators|javadoc=false|lang=xml|url=struts2/apps/showcase/src/main/resources/org/apache/struts2/showcase/validation/QuizAction-validation.xml
{% endcomment %}
 
diff --git a/source/core-developers/client-validation.md b/source/core-developers/client-validation.md
index 9b62a1c..2bf0d89 100644
--- a/source/core-developers/client-validation.md
+++ b/source/core-developers/client-validation.md
@@ -7,12 +7,7 @@ title: Client Validation
 
 Let's create a Client\-Side validation workflow, step by step\.
 
-(information) The `validate` attribute is set to 
-
-~~~~~~~
-true
-~~~~~~~
-\.
+(information) The `validate` attribute is set to `true`\.
 
 (information) Some themes do not support client\-side validation\.
 
diff --git a/source/core-developers/configuration-provider-and-configuration.md b/source/core-developers/configuration-provider-and-configuration.md
index eb0def2..7fddd29 100644
--- a/source/core-developers/configuration-provider-and-configuration.md
+++ b/source/core-developers/configuration-provider-and-configuration.md
@@ -5,12 +5,7 @@ title: Configuration Provider & Configuration
 
 # Configuration Provider & Configuration
 
-The ConfigurationProvider interface describes the framework's configuration\. By default,
the framework loads its configurations via an XML document by using the 
-
-~~~~~~~
-StrutsXmlConfigurationProvider
-~~~~~~~
-\. The provider can be configured through a Dispatcher's [DispatcherListener](dispatcher-listener.html)\.
+The ConfigurationProvider interface describes the framework's configuration\. By default,
the framework loads its configurations via an XML document by using the `StrutsXmlConfigurationProvider`\.
The provider can be configured through a Dispatcher's [DispatcherListener](dispatcher-listener.html)\.
 
 ## Example
 
@@ -37,12 +32,7 @@ StrutsXmlConfigurationProvider
 ~~~~~~~
 ConfigurationProvider
 ~~~~~~~
- is the basic piece of configuration used to tie all the options together in 
-
-~~~~~~~
-ConfigurationManager
-~~~~~~~
-\. There is few different implementations that are already used internally by the Apache
Struts:
+ is the basic piece of configuration used to tie all the options together in `ConfigurationManager`\.
There is few different implementations that are already used internally by the Apache Struts:
 
 + 
 
diff --git a/source/core-developers/file-upload.md b/source/core-developers/file-upload.md
index 8f76c60..0ca04f9 100644
--- a/source/core-developers/file-upload.md
+++ b/source/core-developers/file-upload.md
@@ -55,12 +55,7 @@ If you are using Maven then you can add these libraries as dependencies
in your
 
 ## Basic Usage
 
-The `org.apache.struts2.interceptor.FileUploadInterceptor` class is included as part of the

-
-~~~~~~~
-defaultStack
-~~~~~~~
-\. As long as the required libraries are added to your project you will be able to take advantage
of of the Struts 2 fileUpload capability\. Configure an Action mapping for your Action class
as you typically would\.
+The `org.apache.struts2.interceptor.FileUploadInterceptor` class is included as part of the
`defaultStack`\. As long as the required libraries are added to your project you will be able
to take advantage of of the Struts 2 fileUpload capability\. Configure an Action mapping for
your Action class as you typically would\.
 
 **Example action mapping:**
 
@@ -389,12 +384,7 @@ When the uploaded file type does not match one of the MIME types specified
a fie
 
 __Error Messages__
 
-If an error occurs several field errors will be added assuming that the action implements
`com.opensymphony.xwork2.ValidationAware` or extends 
-
-~~~~~~~
-com.opensymphony.xwork2.ActionSupport
-~~~~~~~
-\. These error messages are based on several i18n values stored in struts\-messages\.properties,
a default i18n file processed for all i18n requests\. You can override the text of these messages
by providing text for the following keys:
+If an error occurs several field errors will be added assuming that the action implements
`com.opensymphony.xwork2.ValidationAware` or extends `com.opensymphony.xwork2.ActionSupport`\.
These error messages are based on several i18n values stored in struts\-messages\.properties,
a default i18n file processed for all i18n requests\. You can override the text of these messages
by providing text for the following keys:
 
 |Error Key|Description|
 |---------|-----------|
@@ -407,12 +397,7 @@ com.opensymphony.xwork2.ActionSupport
 
 __Temporary Directories__
 
-All uploaded files are saved to a temporary directory by the framework before being passed
in to an Action\. Depending on the allowed file sizes it may be necessary to have the framework
store these temporary files in an alternate location\. To do this change `struts.multipart.saveDir`
to the directory where the uploaded files will be placed\. If this property is not set it
defaults to 
-
-~~~~~~~
-javax.servlet.context.tempdir
-~~~~~~~
-\. Keep in mind that on some operating systems, like Solaris, 
+All uploaded files are saved to a temporary directory by the framework before being passed
in to an Action\. Depending on the allowed file sizes it may be necessary to have the framework
store these temporary files in an alternate location\. To do this change `struts.multipart.saveDir`
to the directory where the uploaded files will be placed\. If this property is not set it
defaults to `javax.servlet.context.tempdir`\. Keep in mind that on some operating systems,
like Solaris, 
 
 ~~~~~~~
 /tmp
@@ -448,24 +433,14 @@ The 
 ~~~~~~~
 struts.multipart.validationRegex
 ~~~~~~~
- is used to define a RegEx to be used to validate if the incoming request is a multipart
request\. The request must use the 
-
-~~~~~~~
-POST
-~~~~~~~
- method and match the RegEx, by default the RegEx is defined as follow:
+ is used to define a RegEx to be used to validate if the incoming request is a multipart
request\. The request must use the `POST` method and match the RegEx, by default the RegEx
is defined as follow:
 
 
 ~~~~~~~
 ^multipart\\/form-data(; boundary=[a-zA-Z0-9]{1,70})?
 ~~~~~~~
 
-Please read [RFC1341](https://www\.w3\.org/Protocols/rfc1341/7\_2\_Multipart\.html)^[https://www\.w3\.org/Protocols/rfc1341/7\_2\_Multipart\.html]
the **Multipart section** for more details, existing Struts 
-
-~~~~~~~
-Multipart
-~~~~~~~
- parsers support only 
+Please read [RFC1341](https://www\.w3\.org/Protocols/rfc1341/7\_2\_Multipart\.html)^[https://www\.w3\.org/Protocols/rfc1341/7\_2\_Multipart\.html]
the **Multipart section** for more details, existing Struts `Multipart` parsers support only 
 
 ~~~~~~~
 multipart/form-data
diff --git a/source/core-developers/freemarker-support.md b/source/core-developers/freemarker-support.md
index 6e5c11a..2703e42 100644
--- a/source/core-developers/freemarker-support.md
+++ b/source/core-developers/freemarker-support.md
@@ -5,26 +5,11 @@ title: Freemarker Support
 
 # Freemarker Support
 
-Freemarker views can be rendered using the webwork result type 
-
-~~~~~~~
-freemarker
-~~~~~~~
-\.
+Freemarker views can be rendered using the webwork result type `freemarker`\.
 
 __Configure your action to use the freemarker result type__
 
-The `freemarker` result type is defined in 
-
-~~~~~~~
-struts-default.xml
-~~~~~~~
-, so normally you just include it, and define your resuts to use 
-
-~~~~~~~
-type="freemarker"
-~~~~~~~
-\.
+The `freemarker` result type is defined in `struts-default.xml`, so normally you just include
it, and define your resuts to use `type="freemarker"`\.
 
 
 ~~~~~~~
@@ -46,12 +31,7 @@ Your action properties are automatically resolved \- just like in a velocity
vie
 ~~~~~~~
 ${name
 ~~~~~~~
-\} will result in 
-
-~~~~~~~
-stack.findValue("name")
-~~~~~~~
-, which _generaly_  results in `action.getName()` being executed\.
+\} will result in `stack.findValue("name")`, which _generaly_  results in `action.getName()`
being executed\.
 
 A search process is used to resolve the variable, searching the following scopes in order,
until a value is found :
 
diff --git a/source/core-developers/glassfish-2-x.md b/source/core-developers/glassfish-2-x.md
index bfc1dec..bc66cc2 100644
--- a/source/core-developers/glassfish-2-x.md
+++ b/source/core-developers/glassfish-2-x.md
@@ -7,12 +7,7 @@ title: Glassfish 2.x
 
 __Convention plugin support__
 
-To have proper support of the _Convention Plugin_  in Glassfish 2\.x when packed as EAR
archive add the following constant to 
-
-~~~~~~~
-struts.xml
-~~~~~~~
-
+To have proper support of the _Convention Plugin_  in Glassfish 2\.x when packed as EAR
archive add the following constant to `struts.xml`
 
 
 ~~~~~~~
diff --git a/source/core-developers/jboss-5.md b/source/core-developers/jboss-5.md
index 3fd2fad..1e63959 100644
--- a/source/core-developers/jboss-5.md
+++ b/source/core-developers/jboss-5.md
@@ -7,17 +7,7 @@ title: JBoss 5
 
 __Convention plugin support__
 
-To have proper support of the _Convention Plugin_  in JBoss AS 5, especially when
you put actions inside a jar (which is embedded in war or ear) and not directly into 
-
-~~~~~~~
-WEB-INF/classes
-~~~~~~~
-, you must add the following line into `$JBOSS_HOME/bin/run.conf` or into 
-
-~~~~~~~
-$JBOSS_HOME\bin\run.conf.bat
-~~~~~~~
-
+To have proper support of the _Convention Plugin_  in JBoss AS 5, especially when
you put actions inside a jar (which is embedded in war or ear) and not directly into `WEB-INF/classes`,
you must add the following line into `$JBOSS_HOME/bin/run.conf` or into `$JBOSS_HOME\bin\run.conf.bat`
 **Linux/OSX \- \$JBOSS\_HOME/bin/run\.conf**
 
 
diff --git a/source/core-developers/object-factory.md b/source/core-developers/object-factory.md
index fab7623..581b0b1 100644
--- a/source/core-developers/object-factory.md
+++ b/source/core-developers/object-factory.md
@@ -16,12 +16,7 @@ Customized ObjectFactory must extend ObjectFactory or any of its descendants
and
 
 | 
 
-To register a customized ObjectFactory, add or edit an entry in 
-
-~~~~~~~
-struts.properties
-~~~~~~~
-
+To register a customized ObjectFactory, add or edit an entry in `struts.properties`
 
 
 ~~~~~~~
diff --git a/source/core-developers/parent-package-annotation.md b/source/core-developers/parent-package-annotation.md
index 28644e8..9de2c71 100644
--- a/source/core-developers/parent-package-annotation.md
+++ b/source/core-developers/parent-package-annotation.md
@@ -5,12 +5,7 @@ title: ParentPackage Annotation
 
 # ParentPackage Annotation
 
-The `@ParentPackage` annotation allows the definition of 
-
-~~~~~~~
-Action
-~~~~~~~
-'s package for an action found via [Zero Configuration](zero-configuration.html)\.
+The `@ParentPackage` annotation allows the definition of `Action`'s package for an action
found via [Zero Configuration](zero-configuration.html)\.
 
 ## Usage
 
diff --git a/source/core-developers/pure-java-script-client-side-validation.md b/source/core-developers/pure-java-script-client-side-validation.md
index fac906e..c4f2cab 100644
--- a/source/core-developers/pure-java-script-client-side-validation.md
+++ b/source/core-developers/pure-java-script-client-side-validation.md
@@ -45,9 +45,4 @@ Because client side validation does not talk to the server, the theme (_xhtml
th
 
 __Additional Validator Support__
 
-If you wish to add additional validator support beyond those listed, you may override the
_xhtml theme_  teamplte 
-
-~~~~~~~
-form-close-validate.ftl
-~~~~~~~
-\. This file contains the JavaScript that tries to validate each user\-entered value from
within the browswer\. The _css\_xhtml theme_  extends the _xhtml theme_  and therefore doesn't
have it's own form\-close\-validate\.ftl template\.
+If you wish to add additional validator support beyond those listed, you may override the
_xhtml theme_  teamplte `form-close-validate.ftl`\. This file contains the JavaScript that
tries to validate each user\-entered value from within the browswer\. The _css\_xhtml theme_
 extends the _xhtml theme_  and therefore doesn't have it's own form\-close\-validate\.ftl
template\.
diff --git a/source/core-developers/result-annotation.md b/source/core-developers/result-annotation.md
index 7d277ed..7400477 100644
--- a/source/core-developers/result-annotation.md
+++ b/source/core-developers/result-annotation.md
@@ -27,20 +27,10 @@ In order for `@Result` and `@Results` annotations to be configured correctly
you
 {float}
 ~~~~~~~
 
-+ name \- Result name; default 
-
-~~~~~~~
-Action.SUCCESS
-~~~~~~~
-
++ name \- Result name; default `Action.SUCCESS`
 + value \- Value of result (result destination)
 
-+ type \- Type of result; default 
-
-~~~~~~~
-NullResult
-~~~~~~~
-\. For example:
++ type \- Type of result; default `NullResult`\. For example:
 	
 
   + 
@@ -114,12 +104,7 @@ public class HomeAction extends ActionSupport {
 
 ## @Results – Defining Multiple Results
 
-Defines a set of results for an 
-
-~~~~~~~
-Action
-~~~~~~~
-\.
+Defines a set of results for an `Action`\.
 
 **Defining Multiple Results**
 
diff --git a/source/core-developers/sunone-7-0.md b/source/core-developers/sunone-7-0.md
index 8912c6a..f0695f8 100644
--- a/source/core-developers/sunone-7-0.md
+++ b/source/core-developers/sunone-7-0.md
@@ -21,25 +21,10 @@ grant {
 
 ## Granting Specific Permissions
 
-+ Grant Write Permissions to 
-
-~~~~~~~
-java.util.PropertyPermission
-~~~~~~~
-
-+ Add 
-
-~~~~~~~
-java.lang.reflect.ReflectPermission
-~~~~~~~
- "suppressAccessChecks"
-
-+ Grant all permissions to 
-
-~~~~~~~
-OgnlInvokePermission
-~~~~~~~
++ Grant Write Permissions to `java.util.PropertyPermission`
++ Add `java.lang.reflect.ReflectPermission` "suppressAccessChecks"
 
++ Grant all permissions to `OgnlInvokePermission`
 
 
 ~~~~~~~
diff --git a/source/core-developers/weblogic-6-1.md b/source/core-developers/weblogic-6-1.md
index fea5cc1..dded5d7 100644
--- a/source/core-developers/weblogic-6-1.md
+++ b/source/core-developers/weblogic-6-1.md
@@ -25,12 +25,7 @@ However, the framework code cannot be modifed to do this, because this
will brea
 
 The framework has already been modified slightly to make the above effort possible:
 
-1. **RequestLifecycleFilter** is modified to retrieve its servlet context from the method

-
-~~~~~~~
-getServletContext
-~~~~~~~
-. This method, 
+1. **RequestLifecycleFilter** is modified to retrieve its servlet context from the method
`getServletContext`. This method, 
 
 ~~~~~~~
 getServletContext
@@ -88,11 +83,6 @@ Sometimes BEA Weblogic Server doesn't "rebuild" its temporary files\. 
Do the fo
 
 1. Stop the server.
 
-2. Delete the .wlnotdelete folder in 
-
-~~~~~~~
-mydomain/applications
-~~~~~~~
-.
+2. Delete the .wlnotdelete folder in `mydomain/applications`.
 
 3. Restart the server.
diff --git a/source/core-developers/websphere.md b/source/core-developers/websphere.md
index c35a557..afeb07c 100644
--- a/source/core-developers/websphere.md
+++ b/source/core-developers/websphere.md
@@ -184,12 +184,7 @@ In the diagram, an initial request goes to the Servlet container (such
as Jetty
 
 If the ActionMapper determines that an Action should be invoked, the FilterDispatcher delegates
control to the **ActionProxy**\. The ActionProxy consults the framework [Configuration Files](#PAGE_14163)
manager (initialized from the [struts\.xml](#PAGE_13901) file)\. Next, the ActionProxy creates
an **ActionInvocation**, which is responsible for the command pattern implementation\. This
includes invoking any **Interceptors** (the _before_  clause) in advance of invoking the **Action**
itself\.
 
-Once the Action returns, the ActionInvocation is responsible for looking up the proper **result**
associated with the **Action result code** mapped in 
-
-~~~~~~~
-struts.xml
-~~~~~~~
-\. The result is then executed, which often (but not always, as is the case for [Action Chaining](#PAGE_14214))
involves a template written in _JSP_  or _FreeMarker_  to be rendered\. While rendering, the
templates can use the _Struts Tags_  provided by the framework\. Some of those components
will work with the ActionMapper to render proper URLs for additional requests\.
+Once the Action returns, the ActionInvocation is responsible for looking up the proper **result**
associated with the **Action result code** mapped in `struts.xml`\. The result is then executed,
which often (but not always, as is the case for [Action Chaining](#PAGE_14214)) involves a
template written in _JSP_  or _FreeMarker_  to be rendered\. While rendering, the templates
can use the _Struts Tags_  provided by the framework\. Some of those components will work
with the ActionMapper to [...]
 
 
 
@@ -197,9 +192,4 @@ struts.xml
 
 | 
 
-Interceptors are executed again (in reverse order, calling the _after_  clause)\. Finally,
the response returns through the filters configured in the 
-
-~~~~~~~
-web.xml
-~~~~~~~
-\. If the ActionContextCleanUp filter is present, the FilterDispatcher will _not_  clean
up the ThreadLocal **ActionContext**\. If the ActionContextCleanUp filter is not present,
the FilterDispatcher will cleanup all ThreadLocals\.
+Interceptors are executed again (in reverse order, calling the _after_  clause)\. Finally,
the response returns through the filters configured in the `web.xml`\. If the ActionContextCleanUp
filter is present, the FilterDispatcher will _not_  clean up the ThreadLocal **ActionContext**\.
If the ActionContextCleanUp filter is not present, the FilterDispatcher will cleanup all ThreadLocals\.
diff --git a/source/core-developers/zero-configuration.md b/source/core-developers/zero-configuration.md
index 60331eb..9aadae4 100644
--- a/source/core-developers/zero-configuration.md
+++ b/source/core-developers/zero-configuration.md
@@ -48,12 +48,7 @@ The only example right now is in the showcase, where the person package
uses the
 
 ## Action and Package name
 
-The subpackage name makes the namespace, and the action class name makes the action name\.
 If there is an "Action" suffix, it is dropped before creating the action name\. Therefore,
if the configured package is _com\.myapp\.actions_  and the Action is _com\.myapp\.actions\._
**member**\.EditAction, you can access it via [http://server/myapp/member/edit\.action](http://server/myapp/member/edit\.action)\.
 For multi\-word actions, the first letter is lower\-cased and the rest is left alon [...]
-
-~~~~~~~
-myCustom.action
-~~~~~~~
-\.
+The subpackage name makes the namespace, and the action class name makes the action name\.
 If there is an "Action" suffix, it is dropped before creating the action name\. Therefore,
if the configured package is _com\.myapp\.actions_  and the Action is _com\.myapp\.actions\._
**member**\.EditAction, you can access it via [http://server/myapp/member/edit\.action](http://server/myapp/member/edit\.action)\.
 For multi\-word actions, the first letter is lower\-cased and the rest is left alon [...]
 
 ## Results
 
diff --git a/source/tag-developers/ajax-common-header.md b/source/tag-developers/ajax-common-header.md
index 2b99f94..09fc3c3 100644
--- a/source/tag-developers/ajax-common-header.md
+++ b/source/tag-developers/ajax-common-header.md
@@ -1556,12 +1556,7 @@ Using valueNotifyTopics:
 
 __Caveats__
 
-+ The service that is producing the HTTP Response with JSON response to the Autocompleter
tag must set the HTTP Header Response Content-Type to 
-
-~~~~~~~
-text/json
-~~~~~~~
-. JSON has its own MIME type, which this tag expects.
++ The service that is producing the HTTP Response with JSON response to the Autocompleter
tag must set the HTTP Header Response Content-Type to `text/json`. JSON has its own MIME type,
which this tag expects.
 
 + Since 2.0.9, there is a change in the value:key order. Now, the value **must** come before
the key.
 
diff --git a/source/tag-developers/dojo-autocompleter-tag.md b/source/tag-developers/dojo-autocompleter-tag.md
index 9b2bd48..1486f77 100644
--- a/source/tag-developers/dojo-autocompleter-tag.md
+++ b/source/tag-developers/dojo-autocompleter-tag.md
@@ -1545,12 +1545,7 @@ Using valueNotifyTopics:
 
 __Caveats__
 
-+ The service that is producing the HTTP Response with JSON response to the Autocompleter
tag must set the HTTP Header Response Content-Type to 
-
-~~~~~~~
-text/json
-~~~~~~~
-. JSON has its own MIME type, which this tag expects.
++ The service that is producing the HTTP Response with JSON response to the Autocompleter
tag must set the HTTP Header Response Content-Type to `text/json`. JSON has its own MIME type,
which this tag expects.
 
 + Since 2.0.9, there is a change in the value:key order. Now, the value **must** come before
the key.
 
diff --git a/source/tag-developers/form-tags.md b/source/tag-developers/form-tags.md
index 46b2644..d328e00 100644
--- a/source/tag-developers/form-tags.md
+++ b/source/tag-developers/form-tags.md
@@ -364,24 +364,9 @@ __General Attributes__
 
 __Value/Name Relationship__
 
-In many of the tags (except for the form tag) there is a unique relationship between the
`name` and `value` attributes. The `name` attribute provides the name for the tag, which in
turn is used as the control attribute when the form is submitted. The value submitted is bound
to the 
+In many of the tags (except for the form tag) there is a unique relationship between the
`name` and `value` attributes. The `name` attribute provides the name for the tag, which in
turn is used as the control attribute when the form is submitted. The value submitted is bound
to the `name`. In most cases, the `name` maps to a simple JavaBean property, such as "postalCode".
On a submit, the value would be set to the property by calling the `setPostalCode` mutator.
 
-~~~~~~~
-name
-~~~~~~~
-. In most cases, the `name` maps to a simple JavaBean property, such as "postalCode". On
a submit, the value would be set to the property by calling the `setPostalCode` mutator.
-
-Likewise, a form control could be populated by calling a JavaBean accessor, like 
-
-~~~~~~~
-getPostalCode
-~~~~~~~
-. In the expression language, we can refer to the JavaBean property by name. An expression
like "%{postalCode}" would in turn call 
-
-~~~~~~~
-getPostalCode
-~~~~~~~
-.
+Likewise, a form control could be populated by calling a JavaBean accessor, like `getPostalCode`.
In the expression language, we can refer to the JavaBean property by name. An expression like
"%{postalCode}" would in turn call `getPostalCode`.
 
 
 ~~~~~~~
@@ -392,12 +377,7 @@ getPostalCode
 
 ~~~~~~~
 
-However, since the tags imply a relationship between the `name` and 
-
-~~~~~~~
-value
-~~~~~~~
-, the `value` attribute is optional. If a `value` is not specified, by default, the JavaBean
accessor is used instead.
+However, since the tags imply a relationship between the `name` and `value`, the `value`
attribute is optional. If a `value` is not specified, by default, the JavaBean accessor is
used instead.
 
 
 ~~~~~~~
diff --git a/source/tag-developers/tag-syntax.md b/source/tag-developers/tag-syntax.md
index 3c042cc..2e18302 100644
--- a/source/tag-developers/tag-syntax.md
+++ b/source/tag-developers/tag-syntax.md
@@ -29,21 +29,11 @@ Sometimes, we want to pass the dynamic data to a tag. For example, we
might want
 
 ~~~~~~~
 
-The expression language ([OGNL](#PAGE_14198)) lets us call methods and evaluate properties.
The method `getText` is provided by ActionSupport, which is the base class for most Actions.
Since the Action is on the stack, we can call any of its methods from an expression, including

-
-~~~~~~~
-getText
-~~~~~~~
-.
+The expression language ([OGNL](#PAGE_14198)) lets us call methods and evaluate properties.
The method `getText` is provided by ActionSupport, which is the base class for most Actions.
Since the Action is on the stack, we can call any of its methods from an expression, including
`getText`.
 
 ## Non-String Attributes
 
-The HTTP protocol is text-based, but some tags have non-String attribute types, like `bool`
or 
-
-~~~~~~~
-int
-~~~~~~~
-. To make using non-String attributes intuitative, the framework evaulates **all** non-String
attributes as an expression. In this case, you do not need to use the escape notation. (But,
if you do anyway , the framework will just strip it off.)
+The HTTP protocol is text-based, but some tags have non-String attribute types, like `bool`
or `int`. To make using non-String attributes intuitative, the framework evaulates **all**
non-String attributes as an expression. In this case, you do not need to use the escape notation.
(But, if you do anyway , the framework will just strip it off.)
 
 **Evaluating booleans**
 
@@ -87,17 +77,7 @@ Since it's easy to forget which attributes are String and which are non-String,
 
 ## value is an Object!
 
-Most often, the `value` attribute is set automatically, since `name` attribute usually tells
the framework which property to call to set the 
-
-~~~~~~~
-value
-~~~~~~~
-. But, if there is a reason to set the `value` directly, be advised that 
-
-~~~~~~~
-value
-~~~~~~~
-**is an Object****_NOT_ ****a String**.
+Most often, the `value` attribute is set automatically, since `name` attribute usually tells
the framework which property to call to set the `value`. But, if there is a reason to set
the `value` directly, be advised that `value`**is an Object****_NOT_ ****a String**.
 
  (!)  Since `value` is not a String, whatever is passed to `value` is evaluated as an expression
- **NOT** a String literal.
 
@@ -110,17 +90,7 @@ value
 
 ~~~~~~~
 
-If a `textfield` is passed the value attribute 
-
-~~~~~~~
-"ca"
-~~~~~~~
-, the framework will look for a property named 
-
-~~~~~~~
-getCa
-~~~~~~~
-. Generally, this is not what we mean. What we mean to do is pass a literal String. In the
expression language, literals are placed within quotes
+If a `textfield` is passed the value attribute `"ca"`, the framework will look for a property
named `getCa`. Generally, this is not what we mean. What we mean to do is pass a literal String.
In the expression language, literals are placed within quotes
 
 **Passing a literal value the right way**
 
@@ -131,12 +101,7 @@ getCa
 
 ~~~~~~~
 
-Another approach would be to use the idiom 
-
-~~~~~~~
-value="'ca'"
-~~~~~~~
-, but, in this case, using the expression notation is recommended.
+Another approach would be to use the idiom `value="'ca'"`, but, in this case, using the expression
notation is recommended.
 
 Boiled down, the tag attributes are evaluated using three rules.
 

-- 
To stop receiving notification emails like this one, please contact
['"commits@struts.apache.org" <commits@struts.apache.org>'].

Mime
View raw message