[
https://issues.apache.org/jira/browse/WW-5251?focusedWorklogId=911983&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-911983
]
ASF GitHub Bot logged work on WW-5251:
--------------------------------------
Author: ASF GitHub Bot
Created on: 28/Mar/24 06:53
Start Date: 28/Mar/24 06:53
Worklog Time Spent: 10m
Work Description: kusalk commented on code in PR #898:
URL: https://github.com/apache/struts/pull/898#discussion_r1542400615
##########
core/src/main/java/org/apache/struts2/interceptor/ParameterAware.java:
##########
@@ -0,0 +1,34 @@
+/*
+ * Licensed to the Apache Software Foundation (ASF) under one
+ * or more contributor license agreements. See the NOTICE file
+ * distributed with this work for additional information
+ * regarding copyright ownership. The ASF licenses this file
+ * to you under the Apache License, Version 2.0 (the
+ * "License"); you may not use this file except in compliance
+ * with the License. You may obtain a copy of the License at
+ *
+ * http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing,
+ * software distributed under the License is distributed on an
+ * "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
+ * KIND, either express or implied. See the License for the
+ * specific language governing permissions and limitations
+ * under the License.
+ */
+package org.apache.struts2.interceptor;
+
+import org.apache.struts2.dispatcher.HttpParameters;
+
+import java.util.Map;
+
+@Deprecated
+public interface ParameterAware extends
org.apache.struts2.action.ParametersAware {
+
+ void setParameters(Map map);
+
+ @Override
+ default void withParameters(HttpParameters parameters) {
+ setParameters(parameters);
Review Comment:
Yes that was the approach (bundled compatibility jar) I took when upgrading
my Struts application. This technique can be used for the renamed marker
interfaces only however. The remaining API changes are easy enough to find and
replace in your codebase.
I'll leave it to @lukaszlenart to decide whether we want to restore full API
compatibility with Struts 6.0.0. Given you're upgrading from 2.5 and you're the
first (as far as I know) to complain, I'm inclined to say no.
However, I'm very much in favour of ensuring there are no more SemVer
violations henceforth.
Issue Time Tracking
-------------------
Worklog Id: (was: 911983)
Time Spent: 2h 50m (was: 2h 40m)
> Remove deprecated interfaces used with ServletConfigInterceptor
> ---------------------------------------------------------------
>
> Key: WW-5251
> URL: https://issues.apache.org/jira/browse/WW-5251
> Project: Struts 2
> Issue Type: Improvement
> Components: Core Interceptors
> Reporter: Lukasz Lenart
> Assignee: Lukasz Lenart
> Priority: Major
> Fix For: 7.0.0
>
> Time Spent: 2h 50m
> Remaining Estimate: 0h
>
> {{ServletConfigInterceptor}} supports a bunch of deprecated interfaces which
> already have proper replacement and they should be removed
> * {{org.apache.struts2.util.ServletContextAware}}
> * {{org.apache.struts2.interceptor.ServletRequestAware}}
> * {{org.apache.struts2.interceptor.ServletResponseAware}}
> * {{org.apache.struts2.interceptor.ParameterAware}}
> * {{org.apache.struts2.interceptor.SessionAware}}
> * {{org.apache.struts2.interceptor.ApplicationAware}}
> * {{org.apache.struts2.interceptor.PrincipalAware}}
> all these interfaces have proper replacement in {{org.apache.struts2.action}}
> package
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
