svn commit: r1006138 [1/2] - in /websites/production/struts/content: ./ docs/

2017-02-03 Thread lukaszlenart
Author: lukaszlenart
Date: Fri Feb  3 13:47:41 2017
New Revision: 1006138

Log:
Updates production

Added:
websites/production/struts/content/announce-2016.html
websites/production/struts/content/docs/version-notes-2510.html
Modified:
websites/production/struts/content/announce-2015.html
websites/production/struts/content/announce.html
websites/production/struts/content/docs/ajax-validation.html
websites/production/struts/content/docs/i18n-interceptor.html
websites/production/struts/content/docs/interceptors.html
websites/production/struts/content/docs/migration-guide.html
websites/production/struts/content/docs/security.html
websites/production/struts/content/docs/xsl-result.html
websites/production/struts/content/download.html
websites/production/struts/content/downloads.html
websites/production/struts/content/index.html

Modified: websites/production/struts/content/announce-2015.html
==
--- websites/production/struts/content/announce-2015.html (original)
+++ websites/production/struts/content/announce-2015.html Fri Feb  3 13:47:41 
2017
@@ -7,7 +7,7 @@
   
   
 
-  Announcements
+  Announcements 2015
 
   
   

Added: websites/production/struts/content/announce-2016.html
==
--- websites/production/struts/content/announce-2016.html (added)
+++ websites/production/struts/content/announce-2016.html Fri Feb  3 13:47:41 
2017
@@ -0,0 +1,725 @@
+
+
+
+  
+  
+  
+  
+  
+
+  Announcements 2016
+
+  
+  
+  
+  
+
+  
+  
+  
+
+
+
+http://github.com/apache/struts"; class="github-ribbon">
+  https://s3.amazonaws.com/github/ribbons/forkme_right_red_aa.png"; 
alt="Fork me on GitHub">
+
+
+
+  
+
+  
+
+  
+Menu
+Toggle navigation
+
+
+
+  
+  
+
+
+  
+
+  
+Home
+  
+  
+Welcome
+Downloads
+Announcements
+http://www.apache.org/licenses/";>License
+http://apache.org/foundation/thanks.html";>Thanks!
+http://apache.org/foundation/sponsorship.html";>Sponsorship
+  
+
+
+  
+Support
+  
+  
+User Mailing List
+https://issues.apache.org/jira/browse/WW";>Issue 
Tracker
+Reporting Security Issues
+
+Project info
+Struts 
Core dependencies
+Plugin 
dependencies
+  
+
+
+  
+Documentation
+  
+  
+Birds Eye
+Key Technologies
+Kickstart FAQ
+https://cwiki.apache.org/confluence/display/WW/Home";>Wiki
+
+Getting started
+Tutorials
+FAQs
+Guides
+
+Struts 
Core API
+Plugin APIs
+Tag reference
+http://cwiki.apache.org/S2PLUGINS/home.html";>Plugin registry
+  
+
+
+  
+Contributing
+  
+  
+You at Struts
+How to Help FAQ
+Development Lists
+
+Submitting 
patches
+Source Code
+Coding standards
+
+Release Guidelines
+PMC Charter
+Volunteers
+https://git-wip-us.apache.org/repos/asf?p=struts.git";>Source 
Repository
+  
+
+http://www.apache.org/";>
+  
+
+  
+
+  
+
+
+
+
+  
+Announcements
+
+
+  Skip to: Announcements - 2015
+
+
+19 December 2016 - Struts 2.5.8 General Availability
+
+The Apache Struts group is pleased to announce that Struts 2.5.8 is 
available as a “General Availability”
+release. The GA designation is our highest quality grade.
+
+Apache Struts 2 is an elegant, extensible framework for creating 
enterprise-ready Java web applications.
+The framework is designed to streamline the full development cycle, from 
building, to deploying,
+to maintaining applications over time.
+
+This release addresses one potential security vulnerability:
+
+
+  Possible DoS attack when using URLValidator - S2-044
+
+
+Also this release contains several breaking changes and improvements just 
to mention few of them:
+
+
+  Included XSL files’ URI not being resolved for actions with result 
type="xslt", see WW-2561
+  ConcurrentModificationException 
using s:iterator (intermittent), see 
WW-3019
+  Objec

svn commit: r1006138 [2/2] - in /websites/production/struts/content: ./ docs/

2017-02-03 Thread lukaszlenart
Modified: websites/production/struts/content/docs/interceptors.html
==
--- websites/production/struts/content/docs/interceptors.html (original)
+++ websites/production/struts/content/docs/interceptors.html Fri Feb  3 
13:47:41 2017
@@ -139,15 +139,15 @@ under the License.
 
 
 The default Interceptor stack is 
designed to serve the needs of most applications. Most applications will 
not need to add Interceptors or change the Interceptor 
stack.Many Actions share common concerns. Some Actions need 
input validated. Other Actions may need a file upload to be pre-processed. 
Another Action might need protection from a double submit. Many Actions need 
drop-down lists and other controls pre-populated before the page 
displays.The framework makes it easy to share solutions to these 
concerns using an "Interceptor" strategy. When you request a resource that maps 
to an "action", the framework invokes the Action object. But, before the Action 
is executed, the invocatio
 n can be intercepted by another object. After the Action executes, the 
invocation could be intercepted again. Unsurprisingly, we call these objects 
"Interceptors."/**/
+/*]]>*/
 Understanding 
InterceptorsConfiguring 
InterceptorsStacking Interceptors
 The Default 
Configuration
 Framework 
Interceptors
-Method FilteringInterceptor 
Parameter OverridingInterceptor 
Parameter Overriding InheritanceOrder of Interceptor 
Execution
+Method FilteringInterceptor 
Parameter OverridingInterceptor 
Parameter Overriding InheritanceLazy parametersOrder of Interceptor 
Execution
 FAQNext: Writing Interceptors
 Understanding 
InterceptorsInterceptors can execute code before and after an Action is 
invoked. Most of the framework's core functionality is implemented as 
Interceptors. Features like double-submit guards, type conversion, object 
population, validation, file upload, page preparation, and more, are all 
implemented with the help of Interceptors. Each and every Interceptor is 
pluggable, so you can decide exactly which features an Action needs to 
support.Interceptors can be configured on a per-action basis. Your own 
custom Interceptors can be mixed-and-matched with the Interceptors bundled with 
the framework. Interceptors "set the stage" for the Action classes, doing much 
of the "heavy lifting" before the Action executes.Action LifecyleIn
 some cases, an Interceptor might keep an Action from firing, because of a 
double-submit or because validation failed. Interceptors can also change the 
state of an Action before it executes.The Interceptors are defined in a 
stack that specifies the execution order. In some cases, the order of the 
Interceptors on the stack can be very important.Configuring Interceptorsstruts.xml
 
@@ -156,13 +156,11 @@ div.rbtoc1480661696460 li {margin-left:


 
-   
-
-
- login.jsp
- /secure/home
+   
+  
+  
+  login.jsp
+  /secure/home

 
 
@@ -177,13 +175,11 @@ div.rbtoc1480661696460 li {margin-left:
 
 
 
-
+   
  
  login.jsp
- /secure/home
-
+ /secure/home
+   
 
 
 Looking inside struts-default.xml, we can see how 
it's done.The Default 
Configuration
@@ -250,7 +246,7 @@ div.rbtoc1480661696460 li {margin-left:
 
 
 
-
+svn commit: r1006140 - in /websites/production/struts/content: downloads.html submitting-patches.html

Author: lukaszlenart
Date: Fri Feb  3 14:17:33 2017
New Revision: 1006140

Log:
Updates production

Modified:
websites/production/struts/content/downloads.html
websites/production/struts/content/submitting-patches.html

Modified: websites/production/struts/content/downloads.html
==
--- websites/production/struts/content/downloads.html (original)
+++ websites/production/struts/content/downloads.html Fri Feb  3 14:17:33 2017
@@ -222,6 +222,17 @@
   
   
 
+  Struts 2.5.8
+
+19 December 2016
+
+
+
+  Version notes
+
+  
+  
+
   Struts 2.5.5
 
 21 October 2016

Modified: websites/production/struts/content/submitting-patches.html
==
--- websites/production/struts/content/submitting-patches.html (original)
+++ websites/production/struts/content/submitting-patches.html Fri Feb  3 
14:17:33 2017
@@ -131,7 +131,7 @@
 and done!
 
 Please remember that master branch 
should be used only for small fast commits, if you are working on a large
-change it is better to do it on dedicated branch or even via GitHub.
+change it is better to do it on dedicated branch or even via GitHub (which is 
preferred).
 
 Non-committers
 
@@ -165,14 +165,61 @@ go ahead and create one just right now!
 in top right corner. This will fork the Apache Struts’ repository and will 
create your private (but public) repository
 with the source code.
 
-Next step is to clone your repo locally, information how to do this you 
will find on right sidebar of your repo
-under SSH clone URL headline.
+Next step is to clone your the original repo locally
 
-Now you are ready to work with the Apache Struts’ code base. Perform your 
changes, commit them and
-next push to GitHub! Remember: commit in Git is different than commit in 
Subversion!
+git 
g...@github.com:apache/struts.git
+
+
+
+This will be an origin, you cannot 
push changes to the origin but don’t 
worry, you will use your fork.
+
+Now is time to add your fork as a remote
+
+git remote add 
fork g...@github.com:myusername/struts.git 
+
+
+
+Right now you should have two remotes defined for the repo, origin and fork, use below command to confirm that
+
+git remote -v 
+
+
+
+Now you are ready to work with the Apache Struts’ code base. Start with 
switching to master branch (if not 
already on it)
+
+git checkout master
+
+
+
+now is time to fetch any changes from remote repository
+
+git fetch
+git pull
+
+
+
+you should create a branch to keep your changes and it must be done off the 
master branch
+
+git checkout -b 
my-branch
+
+
 
-With your changes pushed to GitHub you can prepare a Pull Request (short: 
PR). Go to the Apache Struts
-mirror - https://github.com/apache/struts";>https://github.com/apache/struts - 
then to
+Do you changes and commit them to my-branch, when you’re done you can push the 
changes to GitHub, to your fork.
+
+git push -u fork 
my-branch
+
+
+
+If you still need to change something, please remember to comit and push 
changes, but this time you can use just
+
+git push
+
+
+
+as my-branch was already connected 
with remote branch.
+
+The final step is to open a Pull Request (short: PR) against the original 
Apache Struts repo, go to Github. 
+Go to the Apache Struts mirror - https://github.com/apache/struts";>https://github.com/apache/struts - 
then to
 https://github.com/apache/struts/pulls";>Pull request and hit
 https://github.com/apache/struts/compare/";>New Pull Request 
button.
 
@@ -181,6 +228,27 @@ your fork and branch to compare the diff
 
 Finally hit Create Pull Request 
button and you are done!
 
+After your PR got accepted and merged you must clean up your local repo, 
please witch branch to master
+
+git checkout master
+
+
+
+and fetch updates from remote
+
+git fetch -p
+git pull
+
+
+
+and now you can delete your local branch
+
+git branch -d 
my-branch
+
+
+
+and you are ready to start working on another feature/issue.
+
 How to merge Pull Requests
 
 This section is for committers only who want to merge incoming Pull 
Requests. Please remember that the repo at GitHub




svn commit: r1006141 - /websites/production/struts/content/submitting-patches.html

Author: lukaszlenart
Date: Fri Feb  3 14:20:44 2017
New Revision: 1006141

Log:
Updates production

Modified:
websites/production/struts/content/submitting-patches.html

Modified: websites/production/struts/content/submitting-patches.html
==
--- websites/production/struts/content/submitting-patches.html (original)
+++ websites/production/struts/content/submitting-patches.html Fri Feb  3 
14:20:44 2017
@@ -218,9 +218,8 @@ git pull
 
 as my-branch was already connected 
with remote branch.
 
-The final step is to open a Pull Request (short: PR) against the original 
Apache Struts repo, go to Github. 
-Go to the Apache Struts mirror - https://github.com/apache/struts";>https://github.com/apache/struts - 
then to
-https://github.com/apache/struts/pulls";>Pull request and hit
+The final step is to open a Pull Request (short: PR) against the original 
Apache Struts repo. Go to the [Apache Struts 
+mirror]https://github.com/apache/struts), then to https://github.com/apache/struts/pulls";>Pull request and hit
 https://github.com/apache/struts/compare/";>New Pull Request 
button.
 
 If not already selected, click on compare 
across forks. Right now you must select from the dropdowns on right




svn commit: r1006142 - /websites/production/struts/content/submitting-patches.html

Author: lukaszlenart
Date: Fri Feb  3 14:21:33 2017
New Revision: 1006142

Log:
Updates production

Modified:
websites/production/struts/content/submitting-patches.html

Modified: websites/production/struts/content/submitting-patches.html
==
--- websites/production/struts/content/submitting-patches.html (original)
+++ websites/production/struts/content/submitting-patches.html Fri Feb  3 
14:21:33 2017
@@ -218,9 +218,9 @@ git pull
 
 as my-branch was already connected 
with remote branch.
 
-The final step is to open a Pull Request (short: PR) against the original 
Apache Struts repo. Go to the [Apache Struts 
-mirror]https://github.com/apache/struts), then to https://github.com/apache/struts/pulls";>Pull request and hit
-https://github.com/apache/struts/compare/";>New Pull Request 
button.
+The final step is to open a Pull Request (short: PR) against the original 
Apache Struts repo. Go to the 
+https://github.com/apache/struts";>Apache Struts mirror, then to 
https://github.com/apache/struts/pulls";>Pull request
+and hit https://github.com/apache/struts/compare/";>New Pull 
Request button.
 
 If not already selected, click on compare 
across forks. Right now you must select from the dropdowns on right
 your fork and branch to compare the differences with the Apache Struts’ 
master branch.




svn commit: r1006194 - /websites/production/struts/content/docs/migration-guide.html

Author: lukaszlenart
Date: Sat Feb  4 06:24:34 2017
New Revision: 1006194

Log:
Updates production

Modified:
websites/production/struts/content/docs/migration-guide.html

Modified: websites/production/struts/content/docs/migration-guide.html
==
--- websites/production/struts/content/docs/migration-guide.html (original)
+++ websites/production/struts/content/docs/migration-guide.html Sat Feb  4 
06:24:34 2017
@@ -125,7 +125,7 @@ under the License.
 
 
 
-Getting here from there.Version Notes 2.5.xVersion Notes 2.5.9Version Notes 2.5.8Version Notes 2.5.5Version Notes 2.5.2Version Notes 2.5.1Version Notes 2.5Version Notes 2.3.xVersion Notes 2.3.31Version Notes 2.3.30Version Notes 2.3.29Version Notes 2.3.28.1Version Notes 
2.3.28Version 
Notes 2.3.24.3Version Notes 2.3.24.1Version Notes 2.3.24Version Notes 
2.3.20.3Version 
Notes 2.3.20.1Version Notes 2.3.20Version Notes 2.3.16.3Version Notes 
2.3.16.2Version 
Notes 2.3.16.1Version Notes 2.3.16Version Notes 2.3.15.3Version Notes 
2.3.15.2Version 
Notes 2.3.15.1Version Notes 2.3.15Version Notes 2.3.14.3Version Notes 
2.3.14.2Version 
Notes 2.3.14.1Version Notes 2.3.14Version Notes 2.3.12.0Version Notes 2.3.8Version Notes 2.3.7Version Notes 
2.3.4.1Version Notes 
2.3.4Version Notes 2.3.3Version Notes 2.3.1.2Version Notes 
2.3.1.1Version Notes 
2.3.1Version Notes 
2.2.xVersion Notes 
2.2.3.1Version Notes 
2.2.3Version Notes 
2.2.1.1Version Notes 
2.2.1Version Notes 
2.1.xVersion Notes 
2.1.8.1Version Notes 
2.1.8Version Notes 
2.1.6<
 a shape="rect" href="version-notes-215.html">Version Notes 
2.1.5Version Notes 
2.1.4Version Notes 
2.1.3Version Notes 
2.1.2Version Notes 
2.1.1Version Notes 
2.1.0Release Notes 
2.0.xRelease Notes 
2.0.14Release Notes 
2.0.13Release Notes 
2.0.12Release 
Notes 2.0.11.2Release Notes 2.0.11.1Re
 lease Notes 2.0.11Release Notes 2.0.10Release Notes 2.0.9Release Notes 2.0.8Release Notes 2.0.7Release Notes 2.0.6Release Notes 2.0.5Release Notes 2.0.4Release Notes 2.0.3Release Notes 2.0.2Release Notes 2.0.1Release Notes 2.0.0Struts 2.3 to Struts 2.5Struts 2.3 to 2.5 
migrationMigration guide.Struts 1 to Struts 2Comparing Struts 1 and 2How are Struts 1 and Struts 2 
alike? How are they different?Struts 1 
SolutionsVarious issues (and hopefully their solutions!) 
encountered during migrations to Struts 2.Migration StrategiesSteps and overall strategies 
for migrating Struts 1 applications to Struts 2.Migration ToolsDevelopment tools to help aid the migration 
process.Tutorialshttp://www.infoq.com/news/migrating-struts2"; rel="nofollow">Migrating 
Applications to Struts 2 A three-part series by Ian Roughley (Sep 
2006)Roadmaphttp://struts.apache.org/roadmap.html#new";>Roadmap FAQWhat's in store for Struts 
2?http://www.oreillynet.com/onjava/blog/2006/10/my_history_of_struts_2.html";
 rel="nofollow">A History of Struts 2Don Brown's summary of 
eventsWebwork 2.2 to Struts 2Key Changes From WebWork 
2What has been removed or changed from WebWork 2.2 to 
Struts 2WebWork 2 Migration 
StrategiesSteps and overall strategies for migrating WebWork 2 
applications to Struts 2.FAQsWhere do we get 
the latest version the framework?What are some of the 
framework's best features?What is the 
ActionContext?Next: Contributors Guide
+Getting here from there.Version Notes 2.5.xVersion Notes 2.5.10Version Notes 2.5.8Version Notes 2.5.5Version Notes 2.5.2Version Notes 2.5.1Version Notes 2.5Version Notes 2.3.xVersion Notes 2.3.31Version Notes 2.3.30Version Notes 2.3.29Version Notes 2.3.28.1
 Version Notes 
2.3.28Version 
Notes 2.3.24.3Version Notes 2.3.24.1Version Notes 2.3.24Version Notes 
2.3.20.3Version 
Notes 2.3.20.1Version Notes 2.3.20Version Notes 2.3.16.3Version Notes 
2.3.16.2Version 
Notes 2.3.16.1Version Notes 2.3.16Version Notes 2.3.15.3<
 a shape="rect" href="version-notes-23152.html">Version Notes 
2.3.15.2Version 
Notes 2.3.15.1Version Notes 2.3.15Version Notes 2.3.14.3Version Notes 
2.3.14.2Version 
Notes 2.3.14.1Version Notes 2.3.14Version Notes 2.3.12.0Version Notes 2.3.8Version Notes 2.3.7Version Notes 
2.3.4.1Version Notes 
2.3.4Version Notes 2.3.3Version Notes 2.3.1.2Version Notes 
2.3.1.1Version Notes 
2.3.1Version Notes 
2.2.xVersion Notes 
2.2.3.1Version Notes 
2.2.3Version Notes 
2.2.1.1Version Notes 
2.2.1Version Notes 
2.1.xVersion Notes 
2.1.8.1Version Notes 
2.1.8Version Notes 
2.1.6Version Notes 
 >2.1.5Version Notes 
 >2.1.4Version Notes 
 >2.1.3Version Notes 
 >2.1.2Version Notes 
 >2.1.1Version Notes 
 >2.1.0Release Notes 
 >2.0.xRelease 
 >Notes 2.0.14href="release-notes-2013.html">Release Notes 2.0.13shape="rect" href="release-notes-2012.html">Release Notes 
 >2.0.12Release 
 >Notes 2.0.11.2href="release-notes-20111.html">Release Notes 2.0.11.1shape="rect" href="release-notes-2011.html">
 Release Notes 2.0.11Release Notes 2.0.10Release Notes 2.0.9Release Notes 2.0.8Release Notes 2.0.7Release Notes 2.0.6Release N

svn commit: r1006195 - /websites/production/struts/content/submitting-patches.html

Author: lukaszlenart
Date: Sat Feb  4 06:44:27 2017
New Revision: 1006195

Log:
Updates production

Modified:
websites/production/struts/content/submitting-patches.html

Modified: websites/production/struts/content/submitting-patches.html
==
--- websites/production/struts/content/submitting-patches.html (original)
+++ websites/production/struts/content/submitting-patches.html Sat Feb  4 
06:44:27 2017
@@ -204,7 +204,7 @@ git pull
 
 
 
-Do you changes and commit them to my-branch, when you’re done you can push the 
changes to GitHub, to your fork.
+Do your changes and commit them to my-branch, when you’re done you can push the 
changes to GitHub, to your fork.
 
 git push -u fork 
my-branch