[struts-site] branch master updated: Uses tag_parameters to fetch remote content
This is an automated email from the ASF dual-hosted git repository.
lukaszlenart 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 ca31318 Uses tag_parameters to fetch remote content
ca31318 is described below
commit ca313189c6a9b2c3507245b46f64c7db9dc0c733
Author: Lukasz Lenart
AuthorDate: Sat Sep 23 10:34:30 2017 +0200
Uses tag_parameters to fetch remote content
---
source/tag-developers/action-tag.md | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git a/source/tag-developers/action-tag.md
b/source/tag-developers/action-tag.md
index 79e086c..e1bf763 100644
--- a/source/tag-developers/action-tag.md
+++ b/source/tag-developers/action-tag.md
@@ -35,9 +35,7 @@ Is "myAction" null outside the tag? false
## Parameters
-~~~
-{snippet:id=tagattributes|javadoc=false|url=struts2-tags/action.html}
-~~~
+{% tag_parameters action.html %}
## Examples
--
To stop receiving notification emails like this one, please contact
['"commits@struts.apache.org" '].
[struts-site] 02/02: Updates production by Jenkins
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
commit 6de719c3b240dcae183e41de47b480c92cc27871
Author: jenkins
AuthorDate: Sat Sep 23 08:35:43 2017 +
Updates production by Jenkins
---
content/tag-developers/action-tag.html | 77 --
1 file changed, 74 insertions(+), 3 deletions(-)
diff --git a/content/tag-developers/action-tag.html
b/content/tag-developers/action-tag.html
index 8f69cbc..7a04297 100644
--- a/content/tag-developers/action-tag.html
+++ b/content/tag-developers/action-tag.html
@@ -157,9 +157,80 @@ the action cannot be accessed, For example:
Parameters
-{snippet:id=tagattributes|javadoc=false|url=struts2-tags/action.html}
-
-
+
+
+
+ Dynamic Attributes
Allowed: false
+
+
+
+
+
+ Name
+ Required
+ Default
+ Evaluated
+ Type
+ Description
+
+
+ executeResult
+ false
+ false
+ false
+ Boolean
+ Whether
the result of this action (probably a view) should be executed/rendered
+
+
+ flush
+ false
+ true
+ false
+ Boolean
+ Whether
the writer should be flush upon end of action component tag, default to
true
+
+
+ ignoreContextParams
+ false
+ false
+ false
+ Boolean
+ Whether
the request parameters are to be included when the action is invoked
+
+
+ name
+ true
+
+ false
+ String
+ Name of
the action to be executed (without the extension suffix eg. .action)
+
+
+ namespace
+ false
+ namespace
from where tag is used
+ false
+ String
+ Namespace
for action to call
+
+
+ rethrowException
+ false
+ false
+ false
+ Boolean
+ Whether
an exception should be rethrown, if the target action throws an exception
+
+
+ var
+ false
+
+ false
+ String
+ Name used
to reference the value pushed into the Value Stack
+
+
+
Examples
--
To stop receiving notification emails like this one, please contact
"commits@struts.apache.org" .
[struts-site] branch asf-site updated (29a4967 -> 6de719c)
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a change to branch asf-site in repository https://gitbox.apache.org/repos/asf/struts-site.git. from 29a4967 Updates production by Jenkins new cfc58ec Updates production by Jenkins new 6de719c Updates production by Jenkins The 2 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: content/core-developers/chain-result.html | 57 ++- content/core-developers/dispatcher-result.html | 47 +++- content/core-developers/freemarker-result.html | 65 +- content/core-developers/httpheader-result.html | 49 +++- content/core-developers/result-types.html | 2 +- content/tag-developers/action-tag.html | 77 +- 6 files changed, 200 insertions(+), 97 deletions(-) -- To stop receiving notification emails like this one, please contact ['"commits@struts.apache.org" '].
[struts-site] 01/02: Updates production by Jenkins
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
commit cfc58ece6e8aeaad59e18d312834c916bd01411c
Author: jenkins
AuthorDate: Sat Sep 23 06:54:58 2017 +
Updates production by Jenkins
---
content/core-developers/chain-result.html | 57 --
content/core-developers/dispatcher-result.html | 47 +--
content/core-developers/freemarker-result.html | 65 ++
content/core-developers/httpheader-result.html | 49 +--
content/core-developers/result-types.html | 2 +-
5 files changed, 126 insertions(+), 94 deletions(-)
diff --git a/content/core-developers/chain-result.html
b/content/core-developers/chain-result.html
index 41a7d67..0313204 100644
--- a/content/core-developers/chain-result.html
+++ b/content/core-developers/chain-result.html
@@ -129,23 +129,50 @@
https://github.com/apache/struts-site/edit/master/source/core-developers/chain-result.md";
title="Edit this page on GitHub">Edit on GitHub
Chain Result
-{snippet:id=description|javadoc=true|url=com.opensymphony.xwork2.ActionChainResult}
-
+This result invokes an entire other action, complete with it’s own
interceptor stack and result.
+
+Parameters
+
+
+
+actionName (default) - the name
of the action that will be chained to.
+
+
+namespace - used to determine
which namespace the Action is in that we’re chaining. If namespace is null,
this defaults to the current namespace.
+
+
+method - used to specify another
method on target action to be invoked. If null, this defaults to execute
method.
+
+
+skipActions - (optional) the
list of comma separated action names for the actions that could be chained
to.
+
+
+
+Examples
+
+
+
+
+login
+
+
+
+
+
+dashboard
+/secure
+
+
+
+
+
+
+dashboard.jsp
+
+
+
-Parameters
-
-{snippet:id=params|javadoc=true|url=com.opensymphony.xwork2.ActionChainResult}
-
-
-
-Examples
-
-{snippet:id=example|lang=xml|javadoc=true|url=com.opensymphony.xwork2.ActionChainResult}
-
-
-
-
diff --git a/content/core-developers/dispatcher-result.html
b/content/core-developers/dispatcher-result.html
index 4062faa..1578cce 100644
--- a/content/core-developers/dispatcher-result.html
+++ b/content/core-developers/dispatcher-result.html
@@ -129,20 +129,39 @@
https://github.com/apache/struts-site/edit/master/source/core-developers/dispatcher-result.md";
title="Edit this page on GitHub">Edit on GitHub
Dispatcher Result
-{snippet:id=description|javadoc=true|url=org.apache.struts2.result.ServletDispatcherResult}
-
-
-
-#Parameters#
-
-{snippet:id=params|javadoc=true|url=org.apache.struts2.result.ServletDispatcherResult}
-
-
-
-#Examples#
-
-{snippet:id=example|lang=xml|javadoc=true|url=org.apache.struts2.result.ServletDispatcherResult}
-
+Includes or forwards to a view (usually a jsp). Behind the scenes Struts
will use a RequestDispatcher, where the
target servlet/JSP receives the same request/response objects as the original
servlet/JSP. Therefore, you can pass data between them using request.setAttribute() - the Struts action is
available.
+
+There are three possible ways the result can be executed:
+
+
+
+If we are in the scope of a JSP (a PageContext is available),
PageContext’s {@link PageContext#include(String) include} method is called.
+
+
+If there is no PageContext and we’re not in any sort of include (there
is no “javax.servlet.include.servlet_path” in the request attributes), then a
call to {@link RequestDispatcher#forward(javax.servlet.ServletRequest, javax.servlet.ServletResponse) forward
+
+Otherwise, {@link RequestDispatcher#include(javax.servlet.ServletRequest, javax.servlet.ServletResponse) include} is called.
+
+
+
+Parameters
+
+
+
+location (default) - the
location to go to after execution (ex. jsp).
+
+
+parse - true by default. If set
to false, the location param will not be parsed for OGNL expressions.
+
+
+
+Examples
+
+
+ foo.jsp
+
+
diff --git a/content/core-developers/freemarker-result.html
b/content/core-developers/freemarker-result.html
index 0f8f3e2..563cc56 10
[struts-site] 03/03: Ignores some Jekyll specific files
This is an automated email from the ASF dual-hosted git repository. lukaszlenart pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/struts-site.git commit 0225c942cd6225d0b3f241642a98018ae83d8aa5 Author: Lukasz Lenart AuthorDate: Sat Sep 23 17:07:02 2017 +0200 Ignores some Jekyll specific files --- .gitignore | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/.gitignore b/.gitignore index a8d7b1c..4849900 100644 --- a/.gitignore +++ b/.gitignore @@ -3,4 +3,5 @@ content .idea .java-version target -.bundle \ No newline at end of file +.bundle +.jekyll-metadata -- To stop receiving notification emails like this one, please contact "commits@struts.apache.org" .
[struts-site] branch master updated (ca31318 -> 0225c94)
This is an automated email from the ASF dual-hosted git repository. lukaszlenart pushed a change to branch master in repository https://gitbox.apache.org/repos/asf/struts-site.git. from ca31318 Uses tag_parameters to fetch remote content new e4dd1f7 Adds incremental build to speed up local builds new 85d4805 Cleans up tag reference and related pages new 0225c94 Ignores some Jekyll specific files The 3 revisions listed above as "new" are entirely new to this repository and will be described in separate emails. The revisions listed as "add" were already present in the repository and have only been added to this reference. Summary of changes: .gitignore | 3 +- docker/Dockerfile | 2 +- source/tag-developers/extending-themes.md | 145 +++-- source/tag-developers/generic-tag-reference.md | 40 -- .../tag-developers/selecting-template-directory.md | 48 ++- source/tag-developers/selecting-themes.md | 55 +++- source/tag-developers/tag-reference.md | 62 - source/tag-developers/template-loading.md | 123 ++--- source/tag-developers/themes-and-templates.md | 3 - source/tag-developers/ui-tag-reference.md | 58 - source/tag-developers/ui-tags.md | 1 - 11 files changed, 175 insertions(+), 365 deletions(-) delete mode 100644 source/tag-developers/generic-tag-reference.md delete mode 100644 source/tag-developers/ui-tag-reference.md -- To stop receiving notification emails like this one, please contact ['"commits@struts.apache.org" '].
[struts-site] 01/03: Adds incremental build to speed up local builds
This is an automated email from the ASF dual-hosted git repository. lukaszlenart pushed a commit to branch master in repository https://gitbox.apache.org/repos/asf/struts-site.git commit e4dd1f79710203626787435f04e93bcf5cabd845 Author: Lukasz Lenart AuthorDate: Sat Sep 23 16:37:53 2017 +0200 Adds incremental build to speed up local builds --- docker/Dockerfile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docker/Dockerfile b/docker/Dockerfile index b2b050f..d701859 100644 --- a/docker/Dockerfile +++ b/docker/Dockerfile @@ -20,4 +20,4 @@ RUN \ EXPOSE 4000 WORKDIR /srv/jekyll USER jekyll -ENTRYPOINT bundle install && bundle exec jekyll serve --watch --trace --host=0.0.0.0 --force_polling +ENTRYPOINT bundle install && bundle exec jekyll serve --watch --trace --host=0.0.0.0 --force_polling --incremental -- To stop receiving notification emails like this one, please contact "commits@struts.apache.org" .
[struts-site] 02/03: Cleans up tag reference and related pages
This is an automated email from the ASF dual-hosted git repository.
lukaszlenart pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/struts-site.git
commit 85d480509d3ab32ec5972e11970a029d1d91bcae
Author: Lukasz Lenart
AuthorDate: Sat Sep 23 17:06:31 2017 +0200
Cleans up tag reference and related pages
---
source/tag-developers/extending-themes.md | 145 +++--
source/tag-developers/generic-tag-reference.md | 40 --
.../tag-developers/selecting-template-directory.md | 48 ++-
source/tag-developers/selecting-themes.md | 55 +++-
source/tag-developers/tag-reference.md | 62 -
source/tag-developers/template-loading.md | 123 ++---
source/tag-developers/themes-and-templates.md | 3 -
source/tag-developers/ui-tag-reference.md | 58 -
source/tag-developers/ui-tags.md | 1 -
9 files changed, 172 insertions(+), 363 deletions(-)
diff --git a/source/tag-developers/extending-themes.md
b/source/tag-developers/extending-themes.md
index f67c436..bf97cae 100644
--- a/source/tag-developers/extending-themes.md
+++ b/source/tag-developers/extending-themes.md
@@ -4,129 +4,82 @@ title: Tag Developers Guide (WIP)
---
# Extending Themes
+{:.no_toc}
+* Will be replaced with the ToC, excluding a header
+{:toc}
-Most often, an application may just need to override a template (see [Template
Loading](#PAGE_13817)) so that a certain control renders differently. Or, an
application may need to add a new template to an existing theme. Other times,
you might want to create an entirely new theme, perhaps because you are
building a rich set of unique and reusable templates for your organization.
+Most often, an application may just need to override a template (see [Template
Loading](template-loading.html)) so that
+a certain control renders differently. Or, an application may need to add a
new template to an existing theme. Other
+times, you might want to create an entirely new theme, perhaps because you are
building a rich set of unique and reusable
+templates for your organization.
There are three ways to create new themes:
-+ Create a new theme from scratch (**hard!**)
+- Create a new theme from scratch (**hard!**)
+- Wrap an existing theme
+- Extend an existing theme
-+ Wrap an existing theme
+## Creating a New Theme from Scratch
-+ Extend an existing theme
+It's probably never a good idea to create a new theme from scratch. Instead,
use the [simple theme](simple-theme.html)
+as a starting point. The simple theme provides just enough foundation to make
it easy to create new controls by extending
+or wrapping the basic controls. Before starting a new theme, be sure to review
the source templates for all of the provided
+themes. The existing themes are your best guide to creating new themes.
-__Creating a New Theme from Scratch__
+## Wrapping an Existing Theme
+The [xhtml theme](xhtml-theme.html) provides several good examples of the
"wrapping" technique.
+The [simple theme](simple-theme.html) renders the basic control. The xhtml
theme "dresses up" many of the controls
+by adding a header and footer.
-It's probably never a good idea to create a new theme from scratch. Instead,
use the [simple theme](#PAGE_14291) as a starting point. The simple theme
provides just enough foundation to make it easy to create new controls by
extending or wrapping the basic controls. Before starting a new theme, be sure
to review the source templates for all of the provided themes. The existing
themes are your best guide to creating new themes.
+### Wrapping a control
-|
-
-__Wrapping an Existing Theme__
-
-The [xhtml theme](#PAGE_13834) provides several good examples of the
"wrapping" technique. The [simple theme](#PAGE_14291) renders the basic
control. The xhtml theme "dresses up" many of the controls by adding a header
and footer.
-
-**Wrapping a control**
-
-
-~~~
+```html
<#include
"/${parameters.templateDir}/${parameters.expandTheme}/controlheader.ftl" />
<#include "/${parameters.templateDir}/simple/xxx.ftl" />
<#include
"/${parameters.templateDir}/${parameters.expandTheme}/controlfooter.ftl" />
-
-~~~
+```
Wrapping is a great way to augment the basic HTML elements provided by the
simple theme.
-__Extending an Existing Theme__
+### Extending an Existing Theme
-One benefit of object-orientated programming is that it lets us "design by
difference." We can extend an object and code only the behaviour that changes.
Themes provide a similar capability. The subdirectory that hosts a theme can
contain a
-
-~~~
-theme.properties
-~~~
- file. A
-
-~~~
-parent
-~~~
- entry can be added to the property file to designate a theme to extend. The
[ajax theme](#PAGE_14205) extends the [xhtml theme](#PAGE_13834) using this
technique.
+One benefit of object-orientated programming is that it lets
[struts-site] branch asf-site updated: Updates production by Jenkins
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 42619ec Updates production by Jenkins
42619ec is described below
commit 42619eceeb22045fcfd24a18da5e3ce1f359bbfa
Author: jenkins
AuthorDate: Sat Sep 23 15:08:40 2017 +
Updates production by Jenkins
---
content/tag-developers/extending-themes.html | 175 +-
.../selecting-template-directory.html | 58 +
content/tag-developers/selecting-themes.html | 63 ++---
content/tag-developers/tag-reference.html | 259 -
content/tag-developers/template-loading.html | 162 +
content/tag-developers/themes-and-templates.html | 24 +-
content/tag-developers/ui-tags.html| 8 +-
7 files changed, 401 insertions(+), 348 deletions(-)
diff --git a/content/tag-developers/extending-themes.html
b/content/tag-developers/extending-themes.html
index 7a807eb..bf93951 100644
--- a/content/tag-developers/extending-themes.html
+++ b/content/tag-developers/extending-themes.html
@@ -126,157 +126,98 @@
https://github.com/apache/struts-site/edit/master/source/tag-developers/extending-themes.md";
title="Edit this page on GitHub">Edit on GitHub
-Extending Themes
+Extending Themes
+
+
+ Creating a New Theme from
Scratch
+ Wrapping an Existing Theme
+ Wrapping a control
+ Extending an Existing
Theme
+
+
+ Special parameters
+
-Most often, an application may just need to override a template (see Template Loading) so that a certain control renders
differently. Or, an application may need to add a new template to an existing
theme. Other times, you might want to create an entirely new theme, perhaps
because you are building a rich set of unique and reusable templates for your
organization.
+Most often, an application may just need to override a template (see Template Loading) so that
+a certain control renders differently. Or, an application may need to add a
new template to an existing theme. Other
+times, you might want to create an entirely new theme, perhaps because you are
building a rich set of unique and reusable
+templates for your organization.
There are three ways to create new themes:
-
-Create a new theme from scratch (hard!)
-
-
-Wrap an existing theme
-
-
-Extend an existing theme
-
+ Create a new theme from scratch (hard!)
+ Wrap an existing theme
+ Extend an existing theme
-Creating a New Theme from Scratch
-
-It’s probably never a good idea to create a new theme from scratch.
Instead, use the simple theme as a starting point.
The simple theme provides just enough foundation to make it easy to create new
controls by extending or wrapping the basic controls. Before starting a new
theme, be sure to review the source templates for all of the provided themes.
The existing themes are your best guide to creating new themes.
+Creating a New Theme from
Scratch
-
-
-
-
-
-
+It’s probably never a good idea to create a new theme from scratch.
Instead, use the simple theme
+as a starting point. The simple theme provides just enough foundation to make
it easy to create new controls by extending
+or wrapping the basic controls. Before starting a new theme, be sure to review
the source templates for all of the provided
+themes. The existing themes are your best guide to creating new themes.
-Wrapping an Existing Theme
+Wrapping an Existing Theme
-The xhtml theme provides several good examples of
the “wrapping” technique. The simple theme renders
the basic control. The xhtml theme “dresses up” many of the controls by adding
a header and footer.
+The xhtml theme provides several good
examples of the “wrapping” technique.
+The simple theme renders the basic control.
The xhtml theme “dresses up” many of the controls
+by adding a header and footer.
-Wrapping a control
-
-<#include
"/${parameters.templateDir}/${parameters.expandTheme}/controlheader.ftl" />
-<#include "/${parameters.templateDir}/simple/xxx.ftl" />
-<#include
"/${parameters.templateDir}/${parameters.expandTheme}/controlfooter.ftl" />
+Wrapping a control
+<#include
"/${parameters.templateDir}/${parameters.expandTheme}/controlheader.ftl" />
+<#include
"/${parameters.templateDir}/simple/xxx.ftl" />
+<#include
"/${parameters.templateDir}/${parameters.expandTheme}/controlfooter.ftl" />
Wrapping is a great way to augment the basic HTML elements provided by the
simple theme.
-Extending an Existing Theme
+Extending an Existing Theme
-One benefit of object-orientated programming is that it lets us “design by
difference.” We can extend an object and code only the behaviour that changes.
Themes provide a similar capability. The subdirectory that hosts a theme can
