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 4c2e8df Replaces some of old absolute /docs references
4c2e8df is described below
commit 4c2e8dfbc0669f3323c4da79dd5c947375948d5f
Author: Yasser Zamani <yasserzam...@apache.org>
AuthorDate: Wed Nov 22 12:06:02 2017 +0330
Replaces some of old absolute /docs references
---
.../conversion-error-field-validator-annotation.md | 26 +++-------------------
source/core-developers/type-conversion.md | 4 ++++
source/security/index.md | 2 +-
3 files changed, 8 insertions(+), 24 deletions(-)
diff --git
a/source/core-developers/conversion-error-field-validator-annotation.md
b/source/core-developers/conversion-error-field-validator-annotation.md
index 86b9187..1501bf6 100644
--- a/source/core-developers/conversion-error-field-validator-annotation.md
+++ b/source/core-developers/conversion-error-field-validator-annotation.md
@@ -5,28 +5,16 @@ title: ConversionErrorFieldValidator Annotation
# ConversionErrorFieldValidator Annotation
-
-
-{% comment %}start snippet
id=description|javadoc=true|url=com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator
{% endcomment %}
-<p> This validator checks if there are any conversion errors for a field and
applies them if they exist.
- See <a
href="https://struts.apache.org/docs/type-conversion.html#TypeConversion-TypeConversionErrorHandling";>Type
Conversion Error Handling</a> for details.
-</p>
-{% comment %}end snippet
id=description|javadoc=true|url=com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator
{% endcomment %}
+This validator checks if there are any conversion errors for a field and
applies them if they exist.
+See [Type Conversion Error
Handling](type-conversion.html#type-conversion-error-handling) for details.
## Usage
+The `ConversionErrorFieldValidator` annotation must be applied at method level.
-{% comment %}start snippet
id=usage|javadoc=true|url=com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator
{% endcomment %}
-<p> <p>The ConversionErrorFieldValidator annotation must be applied at method
level.</p>
-</p>
-{% comment %}end snippet
id=usage|javadoc=true|url=com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator
{% endcomment %}
-
## Parameters
-
-
-{% comment %}start snippet
id=parameters|javadoc=true|url=com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator
{% endcomment %}
<p> <table class='confluenceTable' summary=''>
<tr>
<th class='confluenceTh'> Parameter </th>
@@ -72,17 +60,9 @@ title: ConversionErrorFieldValidator Annotation
</tr>
</table>
</p>
-{% comment %}end snippet
id=parameters|javadoc=true|url=com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator
{% endcomment %}
## Examples
-
-
-{% comment %}start snippet
id=example|javadoc=true|lang=java|url=com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator
{% endcomment %}
-
```java
@ConversionErrorFieldValidator(message = "Default message", key = "i18n.key",
shortCircuit = true)
-
```
-
-{% comment %}end snippet
id=example|javadoc=true|lang=java|url=com.opensymphony.xwork2.validator.annotations.ConversionErrorFieldValidator
{% endcomment %}
diff --git a/source/core-developers/type-conversion.md
b/source/core-developers/type-conversion.md
index 5cc568c..744c3c0 100644
--- a/source/core-developers/type-conversion.md
+++ b/source/core-developers/type-conversion.md
@@ -4,6 +4,10 @@ title: Type Conversion
---
# Type Conversion
+{:.no_toc}
+
+* Will be replaced with the ToC, excluding a header
+{:toc}
Routine type conversion in the framework is transparent. Generally, all you
need to do is ensure that HTML inputs have
names that can be used in [OGNL](ognl.html) expressions. (HTML inputs are form
elements and other GET/POST parameters.)
diff --git a/source/security/index.md b/source/security/index.md
index da7708f..d79756c 100644
--- a/source/security/index.md
+++ b/source/security/index.md
@@ -16,7 +16,7 @@ The Apache Struts 2 doesn't provide any security mechanism -
it is just a pure w
### Restrict access to the Config Browser Plugin
-[Config Browser
Plugin](https://struts.apache.org/docs/config-browser-plugin.html) exposes
internal configuration and should be used only during development phase. If you
must use it on production site, we strictly recommend restricting access to it
- you can use Basic Authentication or any other security mechanism (e.g.
[Apache Shiro](https://shiro.apache.org/))
+[Config Browser Plugin](../plugins/config-browser/) exposes internal
configuration and should be used only during development phase. If you must use
it on production site, we strictly recommend restricting access to it - you can
use Basic Authentication or any other security mechanism (e.g. [Apache
Shiro](https://shiro.apache.org/))
### Don't mix different access levels in the same namespace
--
To stop receiving notification emails like this one, please contact
['"commits@struts.apache.org" <commits@struts.apache.org>'].
