[struts] branch WW-5309-named-matcher deleted (was 1df2f0a36)
This is an automated email from the ASF dual-hosted git repository. lukaszlenart pushed a change to branch WW-5309-named-matcher in repository https://gitbox.apache.org/repos/asf/struts.git was 1df2f0a36 WW-5309 Supports patterns starting with variable The revisions that were on this branch are still contained in other references; therefore, this change does not discard any commits from the repository.
[struts] 01/01: Merge pull request #686 from apache/WW-5309-named-matcher
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.git commit 50be77a788868919697b7ea18c9ec15315edd08f Merge: c05776177 1df2f0a36 Author: Lukasz Lenart AuthorDate: Fri May 19 12:21:50 2023 +0200 Merge pull request #686 from apache/WW-5309-named-matcher [WW-5309] Supports patterns starting with variable .../xwork2/util/NamedVariablePatternMatcher.java | 4 ++-- .../xwork2/util/NamedVariablePatternMatcherTest.java | 20 2 files changed, 22 insertions(+), 2 deletions(-)
[struts] branch master updated (c05776177 -> 50be77a78)
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.git from c05776177 Merge pull request #685 from apache/WW-5296-dtds add 1df2f0a36 WW-5309 Supports patterns starting with variable new 50be77a78 Merge pull request #686 from apache/WW-5309-named-matcher The 1 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: .../xwork2/util/NamedVariablePatternMatcher.java | 4 ++-- .../xwork2/util/NamedVariablePatternMatcherTest.java | 20 2 files changed, 22 insertions(+), 2 deletions(-)
[struts-site] branch WW-5307-ognl created (now b601bbd71)
This is an automated email from the ASF dual-hosted git repository. lukaszlenart pushed a change to branch WW-5307-ognl in repository https://gitbox.apache.org/repos/asf/struts-site.git at b601bbd71 WW-5307 Cleans up OGNL related pages This branch includes the following new commits: new b601bbd71 WW-5307 Cleans up OGNL related pages The 1 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.
[struts-site] 01/01: WW-5307 Cleans up OGNL related pages
This is an automated email from the ASF dual-hosted git repository. lukaszlenart pushed a commit to branch WW-5307-ognl in repository https://gitbox.apache.org/repos/asf/struts-site.git commit b601bbd719b11e78be937b3e0865e5525a32b815 Author: Lukasz Lenart AuthorDate: Fri May 19 12:49:23 2023 +0200 WW-5307 Cleans up OGNL related pages --- source/tag-developers/ognl-basics.md | 101 --- source/tag-developers/ognl.md| 23 2 files changed, 42 insertions(+), 82 deletions(-) diff --git a/source/tag-developers/ognl-basics.md b/source/tag-developers/ognl-basics.md index 688ab54ab..400087c4a 100644 --- a/source/tag-developers/ognl-basics.md +++ b/source/tag-developers/ognl-basics.md @@ -14,11 +14,11 @@ parent: ## Struts-specific language features -The biggest addition that Struts provides on top of OGNL is the support for the ValueStack. While OGNL operates under +The biggest addition that Struts provides on top of OGNL is the support for the ValueStack. While OGNL operates under the assumption there is only one "root", Struts's ValueStack concept requires there be many "roots". -For example, suppose we are using standard OGNL (not using Struts) and there are two objects in the OgnlContext map: -"foo" -> foo and "bar" -> bar and that the foo object is also configured to be the single **root** object. +For example, suppose we are using standard OGNL (not using Struts) and there are two objects in the OgnlContext map: +"foo" -> foo and "bar" -> bar and that the foo object is also configured to be the single **root** object. The following code illustrates how OGNL deals with these three situations: ``` @@ -27,17 +27,17 @@ The following code illustrates how OGNL deals with these three situations: blah // returns foo.getBlah() because foo is the root ``` -What this means is that OGNL allows many objects in the context, but unless the object you are trying to access is the root, -it must be prepended with a namespaces such as @bar. Now let's talk about how Struts is a little different... +What this means is that OGNL allows many objects in the context, but unless the object you are trying to access is the +root, it must be prepended with a namespaces such as @bar. Now let's talk about how Struts is a little different... -> In Struts, the entire ValueStack is the root object in the context. Rather than having your expressions get the object -> you want from the stack and then get properties from that (ie: peek().blah), Struts has a special OGNL PropertyAccessor -> that will automatically look at the all entries in the stack (from the top down) until it finds an object with the property -> you are looking for. +> In Struts, the entire ValueStack is the root object in the context. Rather than having your expressions get the object +> you want from the stack and then get properties from that (ie: peek().blah), Struts has a special OGNL +> PropertyAccessor that will automatically look at the all entries in the stack (from the top down) until it finds +> an object with the property you are looking for. -For example, suppose the stack contains two objects: Animal and Person. Both objects have a "name" property, Animal has -a "species" property, and Person has a "salary" property. Animal is on the top of the stack, and Person is below it. -The follow code fragments help you get an idea of what is going on here: +For example, suppose the stack contains two objects: `Animal` and `Person`. Both objects have a `name` property, +`Animal` has a `species` property, and `Person` has a `salary` property. `Animal` is on the top of the stack, +and `Person` is below it. The follow code fragments help you get an idea of what is going on here: ``` species// call to animal.getSpecies() @@ -45,29 +45,30 @@ salary // call to person.getSalary() name // call to animal.getName() because animal is on the top ``` -In the last example, there was a tie and so the animal's name was returned. Usually this is the desired effect, but -sometimes you want the property of a lower-level object. To do this, XWork has added support for indexes on the ValueStack. -All you have to do is: +In the last example, there was a tie and so the animal's name was returned. Usually this is the desired effect, but +sometimes you want the property of a lower-level object. To do this, XWork has added support for indexes on the +ValueStack. All you have to do is: ``` [0].name // call to animal.getName() [1].name // call to person.getName() ``` -With expression like `[0] ... [3]` etc. Struts will cut the stack and still return back a CompoundRoot object. To get +With expression like `[0] ... [3]` etc. Struts will cut the stack and still return back a CompoundRoot object. To get the top of that particular stack cut, use `[0].top` -|ognl expression|description| -|---|---| -|`[0].top`|would get the
[struts-site] branch asf-staging updated: Updates stage by Jenkins
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a commit to branch asf-staging in repository https://gitbox.apache.org/repos/asf/struts-site.git The following commit(s) were added to refs/heads/asf-staging by this push: new 4a6ad079f Updates stage by Jenkins 4a6ad079f is described below commit 4a6ad079fde1747ff274282f1fbb85912b40a89f Author: jenkins AuthorDate: Fri May 19 10:55:30 2023 + Updates stage by Jenkins --- content/index.html | 6 ++ content/tag-developers/ognl-basics.html | 98 +++-- content/tag-developers/ognl.html| 24 +++- 3 files changed, 35 insertions(+), 93 deletions(-) diff --git a/content/index.html b/content/index.html index 830f31c69..72d81ba8c 100644 --- a/content/index.html +++ b/content/index.html @@ -177,6 +177,12 @@ +Apache Struts 2.3.x EOL + + The Apache Struts Team informs about discontinuing support for Struts 2.3.x branch, we recommend migration + to the latest version of Struts, read more in + Announcement + diff --git a/content/tag-developers/ognl-basics.html b/content/tag-developers/ognl-basics.html index 9bd857119..4377ccd05 100644 --- a/content/tag-developers/ognl-basics.html +++ b/content/tag-developers/ognl-basics.html @@ -136,7 +136,6 @@ Struts-specific language features Accessing static properties - Differences from the WebWork 1.x EL Struts 2 Named Objects @@ -144,11 +143,11 @@ Struts-specific language features -The biggest addition that Struts provides on top of OGNL is the support for the ValueStack. While OGNL operates under +The biggest addition that Struts provides on top of OGNL is the support for the ValueStack. While OGNL operates under the assumption there is only one “root”, Struts’s ValueStack concept requires there be many “roots”. -For example, suppose we are using standard OGNL (not using Struts) and there are two objects in the OgnlContext map: -“foo” -> foo and “bar” -> bar and that the foo object is also configured to be the single root object. +For example, suppose we are using standard OGNL (not using Struts) and there are two objects in the OgnlContext map: +“foo” -> foo and “bar” -> bar and that the foo object is also configured to be the single root object. The following code illustrates how OGNL deals with these three situations: #foo.blah // returns foo.getBlah() @@ -156,34 +155,34 @@ The following code illustrates how OGNL deals with these three situations: blah // returns foo.getBlah() because foo is the root -What this means is that OGNL allows many objects in the context, but unless the object you are trying to access is the root, -it must be prepended with a namespaces such as @bar. Now let’s talk about how Struts is a little different… +What this means is that OGNL allows many objects in the context, but unless the object you are trying to access is the +root, it must be prepended with a namespaces such as @bar. Now let’s talk about how Struts is a little different… - In Struts, the entire ValueStack is the root object in the context. Rather than having your expressions get the object -you want from the stack and then get properties from that (ie: peek().blah), Struts has a special OGNL PropertyAccessor -that will automatically look at the all entries in the stack (from the top down) until it finds an object with the property -you are looking for. + In Struts, the entire ValueStack is the root object in the context. Rather than having your expressions get the object +you want from the stack and then get properties from that (ie: peek().blah), Struts has a special OGNL +PropertyAccessor that will automatically look at the all entries in the stack (from the top down) until it finds +an object with the property you are looking for. -For example, suppose the stack contains two objects: Animal and Person. Both objects have a “name” property, Animal has -a “species” property, and Person has a “salary” property. Animal is on the top of the stack, and Person is below it. -The follow code fragments help you get an idea of what is going on here: +For example, suppose the stack contains two objects: Animal and Person. Both objects have a name property, +Animal has a species property, and Person has a salary property. Animal is on the top of the stack, +and Person is below it. The follow code fragments help you get an idea of what is going on here: species// call to animal.getSpecies() salary // call to person.getSalary() name // call to animal.getName() because animal is on the top -In the last example, there was a tie and so the animal’s name was returned. Usually this is the desired effect, but -sometimes you want the property of a lower-level object. To do this, XWork has added support for ind
[struts-site] branch WW-5307-ognl updated (b601bbd71 -> 68f40773e)
This is an automated email from the ASF dual-hosted git repository. lukaszlenart pushed a change to branch WW-5307-ognl in repository https://gitbox.apache.org/repos/asf/struts-site.git discard b601bbd71 WW-5307 Cleans up OGNL related pages new 68f40773e WW-5307 Cleans up OGNL related pages This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the branch are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (b601bbd71) \ N -- N -- N refs/heads/WW-5307-ognl (68f40773e) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. The 1 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: source/tag-developers/ognl.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
[struts-site] 01/01: WW-5307 Cleans up OGNL related pages
This is an automated email from the ASF dual-hosted git repository. lukaszlenart pushed a commit to branch WW-5307-ognl in repository https://gitbox.apache.org/repos/asf/struts-site.git commit 68f40773e63a8e749c7af00bdc9b9fe2e157df24 Author: Lukasz Lenart AuthorDate: Fri May 19 12:49:23 2023 +0200 WW-5307 Cleans up OGNL related pages --- source/tag-developers/ognl-basics.md | 101 --- source/tag-developers/ognl.md| 23 2 files changed, 42 insertions(+), 82 deletions(-) diff --git a/source/tag-developers/ognl-basics.md b/source/tag-developers/ognl-basics.md index 688ab54ab..400087c4a 100644 --- a/source/tag-developers/ognl-basics.md +++ b/source/tag-developers/ognl-basics.md @@ -14,11 +14,11 @@ parent: ## Struts-specific language features -The biggest addition that Struts provides on top of OGNL is the support for the ValueStack. While OGNL operates under +The biggest addition that Struts provides on top of OGNL is the support for the ValueStack. While OGNL operates under the assumption there is only one "root", Struts's ValueStack concept requires there be many "roots". -For example, suppose we are using standard OGNL (not using Struts) and there are two objects in the OgnlContext map: -"foo" -> foo and "bar" -> bar and that the foo object is also configured to be the single **root** object. +For example, suppose we are using standard OGNL (not using Struts) and there are two objects in the OgnlContext map: +"foo" -> foo and "bar" -> bar and that the foo object is also configured to be the single **root** object. The following code illustrates how OGNL deals with these three situations: ``` @@ -27,17 +27,17 @@ The following code illustrates how OGNL deals with these three situations: blah // returns foo.getBlah() because foo is the root ``` -What this means is that OGNL allows many objects in the context, but unless the object you are trying to access is the root, -it must be prepended with a namespaces such as @bar. Now let's talk about how Struts is a little different... +What this means is that OGNL allows many objects in the context, but unless the object you are trying to access is the +root, it must be prepended with a namespaces such as @bar. Now let's talk about how Struts is a little different... -> In Struts, the entire ValueStack is the root object in the context. Rather than having your expressions get the object -> you want from the stack and then get properties from that (ie: peek().blah), Struts has a special OGNL PropertyAccessor -> that will automatically look at the all entries in the stack (from the top down) until it finds an object with the property -> you are looking for. +> In Struts, the entire ValueStack is the root object in the context. Rather than having your expressions get the object +> you want from the stack and then get properties from that (ie: peek().blah), Struts has a special OGNL +> PropertyAccessor that will automatically look at the all entries in the stack (from the top down) until it finds +> an object with the property you are looking for. -For example, suppose the stack contains two objects: Animal and Person. Both objects have a "name" property, Animal has -a "species" property, and Person has a "salary" property. Animal is on the top of the stack, and Person is below it. -The follow code fragments help you get an idea of what is going on here: +For example, suppose the stack contains two objects: `Animal` and `Person`. Both objects have a `name` property, +`Animal` has a `species` property, and `Person` has a `salary` property. `Animal` is on the top of the stack, +and `Person` is below it. The follow code fragments help you get an idea of what is going on here: ``` species// call to animal.getSpecies() @@ -45,29 +45,30 @@ salary // call to person.getSalary() name // call to animal.getName() because animal is on the top ``` -In the last example, there was a tie and so the animal's name was returned. Usually this is the desired effect, but -sometimes you want the property of a lower-level object. To do this, XWork has added support for indexes on the ValueStack. -All you have to do is: +In the last example, there was a tie and so the animal's name was returned. Usually this is the desired effect, but +sometimes you want the property of a lower-level object. To do this, XWork has added support for indexes on the +ValueStack. All you have to do is: ``` [0].name // call to animal.getName() [1].name // call to person.getName() ``` -With expression like `[0] ... [3]` etc. Struts will cut the stack and still return back a CompoundRoot object. To get +With expression like `[0] ... [3]` etc. Struts will cut the stack and still return back a CompoundRoot object. To get the top of that particular stack cut, use `[0].top` -|ognl expression|description| -|---|---| -|`[0].top`|would get the
[struts-site] branch asf-staging updated: Updates stage by Jenkins
This is an automated email from the ASF dual-hosted git repository. git-site-role pushed a commit to branch asf-staging in repository https://gitbox.apache.org/repos/asf/struts-site.git The following commit(s) were added to refs/heads/asf-staging by this push: new 024cdb9eb Updates stage by Jenkins 024cdb9eb is described below commit 024cdb9eb589a8f28b749f8729f187db27655577 Author: jenkins AuthorDate: Fri May 19 11:17:36 2023 + Updates stage by Jenkins --- content/tag-developers/ognl.html | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/tag-developers/ognl.html b/content/tag-developers/ognl.html index 1b5708ea6..a2f11c32e 100644 --- a/content/tag-developers/ognl.html +++ b/content/tag-developers/ognl.html @@ -138,7 +138,7 @@ Lambda Expressions -OGNL is the Object Graph Navigation Language (see https://github.com/orphan-oss/ognl";>OGNL page for the full +OGNL is the Object Graph Navigation Language (see https://ognl.orphan.software/";>OGNL page for the full documentation of OGNL). Here, we will cover a few examples of OGNL features that co-exist with the framework. To review basic concepts, refer to OGNL Basics.
