[jira] [Updated] (WW-4858) JSONInterceptor must not populate value stack directly

2024-01-16 Thread Lukasz Lenart (Jira) 


 [ 
https://issues.apache.org/jira/browse/WW-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lukasz Lenart updated WW-4858:
--
Fix Version/s: 6.5.0
   (was: 6.4.0)

> JSONInterceptor must not populate value stack directly
> --
>
> Key: WW-4858
> URL: https://issues.apache.org/jira/browse/WW-4858
> Project: Struts 2
>  Issue Type: Improvement
>  Components: Plugin - JSON
>Affects Versions: 2.3.1, 6.1.1
>Reporter: Yasser Zamani
>Priority: Major
>  Labels: decouple, refactoring
> Fix For: 6.5.0
>
> Attachments: StrutsUnifiedDataModel.png
>
>
> {{JSONInterceptor}} must populate value stack via OGNL to honor our 
> exclusions!
> So according to my current quick view and understanding, I'm planning 
> something like below which also resolves WW-3364: {{JSONInterceptor}} could 
> be an extension of {{ModelDrivenInterceptor}} via some refactoring of both. 
> From hereafter, {{JSONPopulator}} could be removed and {{JSONInterceptor}} 
> must give population up to {{ParametersInterceptor}}. This simply could be 
> achieved by something like pushing {{JSONInterceptor.root}} into top of stack 
> and also moving posted json to http params (or if was impossible some 
> refactoring of {{ParametersInterceptor}}).
> Please cast here any objections, votes or idea.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (WW-4858) JSONInterceptor must not populate value stack directly

2023-06-28 Thread Lukasz Lenart (Jira) 


 [ 
https://issues.apache.org/jira/browse/WW-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lukasz Lenart updated WW-4858:
--
Fix Version/s: 6.4.0
   (was: 6.2.0)

> JSONInterceptor must not populate value stack directly
> --
>
> Key: WW-4858
> URL: https://issues.apache.org/jira/browse/WW-4858
> Project: Struts 2
>  Issue Type: Improvement
>  Components: Plugin - JSON
>Affects Versions: 2.3.1, 6.1.1
>Reporter: Yasser Zamani
>Priority: Major
>  Labels: decouple, refactoring
> Fix For: 6.4.0
>
> Attachments: StrutsUnifiedDataModel.png
>
>
> {{JSONInterceptor}} must populate value stack via OGNL to honor our 
> exclusions!
> So according to my current quick view and understanding, I'm planning 
> something like below which also resolves WW-3364: {{JSONInterceptor}} could 
> be an extension of {{ModelDrivenInterceptor}} via some refactoring of both. 
> From hereafter, {{JSONPopulator}} could be removed and {{JSONInterceptor}} 
> must give population up to {{ParametersInterceptor}}. This simply could be 
> achieved by something like pushing {{JSONInterceptor.root}} into top of stack 
> and also moving posted json to http params (or if was impossible some 
> refactoring of {{ParametersInterceptor}}).
> Please cast here any objections, votes or idea.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (WW-4858) JSONInterceptor must not populate value stack directly

2022-10-22 Thread Lukasz Lenart (Jira) 


 [ 
https://issues.apache.org/jira/browse/WW-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lukasz Lenart updated WW-4858:
--
Fix Version/s: 6.2.0
   (was: 6.1.0)

> JSONInterceptor must not populate value stack directly
> --
>
> Key: WW-4858
> URL: https://issues.apache.org/jira/browse/WW-4858
> Project: Struts 2
>  Issue Type: Improvement
>  Components: Plugin - JSON
>Affects Versions: 2.3.1, 6.1.0
>Reporter: Yasser Zamani
>Priority: Major
>  Labels: decouple, refactoring
> Fix For: 6.2.0
>
> Attachments: StrutsUnifiedDataModel.png
>
>
> {{JSONInterceptor}} must populate value stack via OGNL to honor our 
> exclusions!
> So according to my current quick view and understanding, I'm planning 
> something like below which also resolves WW-3364: {{JSONInterceptor}} could 
> be an extension of {{ModelDrivenInterceptor}} via some refactoring of both. 
> From hereafter, {{JSONPopulator}} could be removed and {{JSONInterceptor}} 
> must give population up to {{ParametersInterceptor}}. This simply could be 
> achieved by something like pushing {{JSONInterceptor.root}} into top of stack 
> and also moving posted json to http params (or if was impossible some 
> refactoring of {{ParametersInterceptor}}).
> Please cast here any objections, votes or idea.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

[jira] [Updated] (WW-4858) JSONInterceptor must not populate value stack directly

2021-12-12 Thread Lukasz Lenart (Jira) 


 [ 
https://issues.apache.org/jira/browse/WW-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Lukasz Lenart updated WW-4858:
--
Fix Version/s: 2.6.1
   (was: 2.6)

> JSONInterceptor must not populate value stack directly
> --
>
> Key: WW-4858
> URL: https://issues.apache.org/jira/browse/WW-4858
> Project: Struts 2
>  Issue Type: Improvement
>  Components: Plugin - JSON
>Affects Versions: 2.3.1, 2.5.x
>Reporter: Yasser Zamani
>Priority: Major
>  Labels: decouple, refactoring
> Fix For: 2.6.1
>
> Attachments: StrutsUnifiedDataModel.png
>
>
> {{JSONInterceptor}} must populate value stack via OGNL to honor our 
> exclusions!
> So according to my current quick view and understanding, I'm planning 
> something like below which also resolves WW-3364: {{JSONInterceptor}} could 
> be an extension of {{ModelDrivenInterceptor}} via some refactoring of both. 
> From hereafter, {{JSONPopulator}} could be removed and {{JSONInterceptor}} 
> must give population up to {{ParametersInterceptor}}. This simply could be 
> achieved by something like pushing {{JSONInterceptor.root}} into top of stack 
> and also moving posted json to http params (or if was impossible some 
> refactoring of {{ParametersInterceptor}}).
> Please cast here any objections, votes or idea.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

[jira] [Updated] (WW-4858) JSONInterceptor must not populate value stack directly

2018-06-12 Thread Yasser Zamani (JIRA) 


 [ 
https://issues.apache.org/jira/browse/WW-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yasser Zamani updated WW-4858:
--
Fix Version/s: (was: 2.3.x)
   (was: 2.5.x)
   2.6

> JSONInterceptor must not populate value stack directly
> --
>
> Key: WW-4858
> URL: https://issues.apache.org/jira/browse/WW-4858
> Project: Struts 2
>  Issue Type: Improvement
>  Components: Plugin - JSON
>Affects Versions: 2.3.x, 2.5.x
>Reporter: Yasser Zamani
>Priority: Major
>  Labels: decouple, refactoring
> Fix For: 2.6
>
> Attachments: StrutsUnifiedDataModel.png
>
>
> {{JSONInterceptor}} must populate value stack via OGNL to honor our 
> exclusions!
> So according to my current quick view and understanding, I'm planning 
> something like below which also resolves WW-3364: {{JSONInterceptor}} could 
> be an extension of {{ModelDrivenInterceptor}} via some refactoring of both. 
> From hereafter, {{JSONPopulator}} could be removed and {{JSONInterceptor}} 
> must give population up to {{ParametersInterceptor}}. This simply could be 
> achieved by something like pushing {{JSONInterceptor.root}} into top of stack 
> and also moving posted json to http params (or if was impossible some 
> refactoring of {{ParametersInterceptor}}).
> Please cast here any objections, votes or idea.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (WW-4858) JSONInterceptor must not populate value stack directly

2017-10-05 Thread Yasser Zamani (JIRA) 

 [ 
https://issues.apache.org/jira/browse/WW-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yasser Zamani updated WW-4858:
--
Fix Version/s: (was: 2.3.35)
   (was: 2.5.14)
   2.5.x
   2.3.x

> JSONInterceptor must not populate value stack directly
> --
>
> Key: WW-4858
> URL: https://issues.apache.org/jira/browse/WW-4858
> Project: Struts 2
>  Issue Type: Improvement
>  Components: Plugin - JSON
>Affects Versions: 2.3.x, 2.5.x
>Reporter: Yasser Zamani
>  Labels: decouple, refactoring
> Fix For: 2.3.x, 2.5.x
>
> Attachments: StrutsUnifiedDataModel.png
>
>
> {{JSONInterceptor}} must populate value stack via OGNL to honor our 
> exclusions!
> So according to my current quick view and understanding, I'm planning 
> something like below which also resolves WW-3364: {{JSONInterceptor}} could 
> be an extension of {{ModelDrivenInterceptor}} via some refactoring of both. 
> From hereafter, {{JSONPopulator}} could be removed and {{JSONInterceptor}} 
> must give population up to {{ParametersInterceptor}}. This simply could be 
> achieved by something like pushing {{JSONInterceptor.root}} into top of stack 
> and also moving posted json to http params (or if was impossible some 
> refactoring of {{ParametersInterceptor}}).
> Please cast here any objections, votes or idea.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (WW-4858) JSONInterceptor must not populate value stack directly

2017-09-20 Thread Yasser Zamani (JIRA) 

 [ 
https://issues.apache.org/jira/browse/WW-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yasser Zamani updated WW-4858:
--
Attachment: StrutsUnifiedDataModel.png

> JSONInterceptor must not populate value stack directly
> --
>
> Key: WW-4858
> URL: https://issues.apache.org/jira/browse/WW-4858
> Project: Struts 2
>  Issue Type: Improvement
>  Components: Plugin - JSON
>Affects Versions: 2.3.x, 2.5.x
>Reporter: Yasser Zamani
>  Labels: decouple, refactoring
> Fix For: 2.3.35, 2.5.14
>
> Attachments: StrutsUnifiedDataModel.png
>
>
> {{JSONInterceptor}} must populate value stack via OGNL to honor our 
> exclusions!
> So according to my current quick view and understanding, I'm planning 
> something like below which also resolves WW-3364: {{JSONInterceptor}} could 
> be an extension of {{ModelDrivenInterceptor}} via some refactoring of both. 
> From hereafter, {{JSONPopulator}} could be removed and {{JSONInterceptor}} 
> must give population up to {{ParametersInterceptor}}. This simply could be 
> achieved by something like pushing {{JSONInterceptor.root}} into top of stack 
> and also moving posted json to http params (or if was impossible some 
> refactoring of {{ParametersInterceptor}}).
> Please cast here any objections, votes or idea.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

[jira] [Updated] (WW-4858) JSONInterceptor must not populate value stack directly

2017-09-16 Thread Yasser Zamani (JIRA) 

 [ 
https://issues.apache.org/jira/browse/WW-4858?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yasser Zamani updated WW-4858:
--
Description: 
{{JSONInterceptor}} must populate value stack via OGNL to honor our exclusions!

So according to my current quick view and understanding, I'm planning something 
like below which also resolves WW-3364: {{JSONInterceptor}} could be an 
extension of {{ModelDrivenInterceptor}} via some refactoring of both. From 
hereafter, {{JSONPopulator}} could be removed and {{JSONInterceptor}} must give 
population up to {{ParametersInterceptor}}. This simply could be achieved by 
something like pushing {{JSONInterceptor.root}} into top of stack and also 
moving posted json to http params (or if was impossible some refactoring of 
{{ParametersInterceptor}}).

Please cast here any objections, votes or idea.

  was:
{{JSONInterceptor}} must populate value stack via OGNL to honor our exclusions!

So according to my current quick view and understanding, I'm planning something 
like below which also resolves WW-3364: {{JSONInterceptor}} could be an 
extension of {{ModelDrivenInterceptor}} via some refactoring of both. From 
hereafter, {{JSONPopulator}} could be removed and {{JSONInterceptor}} must give 
population up to {{ParametersInterceptor}}. This simply could be achieved by 
something like pushing {{JSONInterceptor.root}} into top of stack and also 
moving posted json to http params (or if was impossible some refactoring of 
{{ParametersInterceptor}}).

If you had any objections, votes or idea, please cast here as I'm going to 
start after merge of [#167|https://github.com/apache/struts/pull/167].


> JSONInterceptor must not populate value stack directly
> --
>
> Key: WW-4858
> URL: https://issues.apache.org/jira/browse/WW-4858
> Project: Struts 2
>  Issue Type: Improvement
>  Components: Plugin - JSON
>Affects Versions: 2.3.x, 2.5.x
>Reporter: Yasser Zamani
>  Labels: decouple, refactoring
> Fix For: 2.3.35, 2.5.14
>
>
> {{JSONInterceptor}} must populate value stack via OGNL to honor our 
> exclusions!
> So according to my current quick view and understanding, I'm planning 
> something like below which also resolves WW-3364: {{JSONInterceptor}} could 
> be an extension of {{ModelDrivenInterceptor}} via some refactoring of both. 
> From hereafter, {{JSONPopulator}} could be removed and {{JSONInterceptor}} 
> must give population up to {{ParametersInterceptor}}. This simply could be 
> achieved by something like pushing {{JSONInterceptor.root}} into top of stack 
> and also moving posted json to http params (or if was impossible some 
> refactoring of {{ParametersInterceptor}}).
> Please cast here any objections, votes or idea.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)