Github user aleksandr-m commented on the issue:
https://github.com/apache/struts/pull/118
Let's break it down:
**chain**
First of all using `chain` is discouraged. Proxying the action itself is
not the best practice too.
If the only viable solution to know target class is to declare a real class
of the bean then it should be done in the chain interceptor not in the action
configuration.
**json result**
What is the problem with generating proxy data into json? What if this is
what is really needed?
**excluding `ActionSupport`**
If `ActionSupport` is excluded then its methods cannot be used in the JSP
(e.g. `getText`). In case of `chain` action errors / messages won't be moved to
the next action. Etc.
**overall**
*someone may successfully change proxy information of the action by an HTTP
request with named parameters*
Are you sure? Can you provide some example?
*there is no any clean way to check if it's a proxy and unwrap it to target
class*
How knowing the name of the real class helps in that case? What are you
going to do with it?
If it is spring proxy then there are helper methods to get target class
from the instance (e.g. `AopUtils`). If there is no *clean* way to do this in
the Struts core utility class then it can be delegated to current object
factory.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org
For additional commands, e-mail: dev-h...@struts.apache.org
