[
https://issues.apache.org/jira/browse/WW-5490?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17901977#comment-17901977
]
nikos dimitrakas edited comment on WW-5490 at 11/29/24 7:15 PM:
----------------------------------------------------------------
But that case is about ValidationInterceptor and other classes that have not
yet been migrated. That is fine. But with ValueStack, that class has been
migrated and deprecated, but is still being used by other classes (like
TextField). I am not suggesting that all classes should be migrated to the new
package, I am only saying that TextField and other classes should use the
ValueStack class in the new package. Thus avoiding using deprecated classes
internally.
was (Author: nikos):
But that case is about ValidationInterceptor and other classes that have not
yet been migrated. That is fine. But with ValueStack, that class has been
migrated and deprecated, but is still being used by other classes (like
TextField). I am not suggesting that TextField should be migrated to the new
package. I am only saying that TextField while it is still in the old package,
it should use the ValueStack class in the new package. Thus avoiding using
deprecated classes internally.
> Deprecated ValueStack still being used
> --------------------------------------
>
> Key: WW-5490
> URL: https://issues.apache.org/jira/browse/WW-5490
> Project: Struts 2
> Issue Type: Improvement
> Affects Versions: 6.7.0
> Reporter: nikos dimitrakas
> Priority: Major
> Fix For: 6.7.0
>
>
> com.opensymphony.xwork2.util.ValueStack got deprecated in 6.7.0 (according to
> WW-3714) but many classes in org.apache.struts2.components (like TextField,
> TextArea) still use it. Is it intentional or were they missed?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
