removing warnings

This commit is contained in:
Mark Fisher
2010-11-09 17:22:38 -05:00
parent 1faa9f08b0
commit 304abda2d3
2 changed files with 3 additions and 5 deletions

View File

@@ -45,8 +45,7 @@ import org.springframework.util.Assert;
* is used. It ensures files are picked up only once from the directory.
* <p/>
* A common problem with reading files is that a file may be detected before it
* is ready. The default
* {@link AcceptOnceEntryFileListFilter}
* is ready. The default {@link AcceptOnceFileListFilter}
* does not prevent this. In most cases, this can be prevented if the
* file-writing process renames each file as soon as it is ready for reading. A
* pattern-matching filter that accepts only files that are ready (e.g. based on

View File

@@ -55,8 +55,7 @@ public abstract class AbstractInboundRemoteFileSystemSychronizer<F> extends Abst
protected volatile FileListFilter<F> filter = new AcceptAllFileListFilter<F>();
/**
* The {@link ScheduledFuture} instance we get when we
* schedule our {@link SynchronizeTask}
* The {@link ScheduledFuture} instance we get when we schedule our SynchronizeTask.
*/
protected ScheduledFuture<?> scheduledFuture;
@@ -88,7 +87,7 @@ public abstract class AbstractInboundRemoteFileSystemSychronizer<F> extends Abst
* {@link EntryAcknowledgmentStrategy#acknowledge(Object, Object)} will be called in line with the
* {@link org.springframework.integration.core.MessageSource#receive()} call so this could conceivably
* be a 'live' stateful client (a connection?) that is inappropriate to cache as it has per-request state.
* @param t
* @param file
* leverages strategy implementations to enable different
* behavior. It's a hook to the file entry after it's been
* successfully downloaded. Conceptually, you might delete the