You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@struts.apache.org by "Yasser Zamani (JIRA)" <ji...@apache.org> on 2017/10/06 06:57:00 UTC
[jira] [Updated] (WW-4858) JSONInterceptor must not populate value
stack directly
[ 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)