Spring/spring-integration
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Remove not used any more ImapIdleChannelAdapter.receivingTask property

Browse Source 
The logic for the `ImapIdleChannelAdapter` was changed to not use `TaskScheduler`. 
When that was done the `ScheduledFuture<?> receivingTask` from the `ImapIdleChannelAdapter` was not removed.
This commit is contained in:
Filip Hrisafov
2024-10-14 23:54:45 +02:00
committed by GitHub
parent d5ab03c0c7
commit 1de81b6717
1 changed files with 0 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
spring-integration-mail/src/main/java/org/springframework/integration/mail/ImapIdleChannelAdapter.java
View File

@@ -19,7 +19,6 @@ package org.springframework.integration.mail;
import java.io.Serial;
import java.util.List;
import java.util.concurrent.Executor;
import java.util.concurrent.ScheduledFuture;
import java.util.function.Consumer;
import jakarta.mail.Folder;
@@ -79,8 +78,6 @@ public class ImapIdleChannelAdapter extends MessageProducerSupport implements Be
private long reconnectDelay = DEFAULT_RECONNECT_DELAY; // milliseconds
private volatile ScheduledFuture<?> receivingTask;
public ImapIdleChannelAdapter(ImapMailReceiver mailReceiver) {
Assert.notNull(mailReceiver, "'mailReceiver' must not be null");
this.mailReceiver = mailReceiver;
@@ -171,10 +168,6 @@ public class ImapIdleChannelAdapter extends MessageProducerSupport implements Be
@Override
// guarded by super#lifecycleLock
protected void doStop() {
if (this.receivingTask != null) {
this.receivingTask.cancel(true);
this.receivingTask = null;
}
this.mailReceiver.cancelPing();
}