Interface DocumentEventFilenameMatcher

All Known Implementing Classes:
DocumentEventFilenameMatcher.EndsWithFilenameMatcher, DocumentEventFilenameMatcher.EqualsFilenameMatcher, DocumentEventFilenameMatcher.RegexFilenameMatcher, DocumentEventFilenameMatcher.StartsWithFilenameMatcher
Functional Interface:
This is a functional interface and can therefore be used as the assignment target for a lambda expression or method reference.
@FunctionalInterface public interface DocumentEventFilenameMatcher
Strategy applied to a matched content-item filename by activity-bound Document Event behaviors as a post-dispatch check before progressing the execution. One implementation per DocumentEventFilenameFilter.MODE_EQUALS, DocumentEventFilenameFilter.MODE_STARTS_WITH, DocumentEventFilenameFilter.MODE_ENDS_WITH and DocumentEventFilenameFilter.MODE_REGEX; ACCEPT_ALL stands in when no filter is configured and REJECT_ALL when the configuration is invalid (unknown mode or a regex that fails to compile — the validator catches both at deploy time, so this is just a defense-in-depth fallback).

Use from(DocumentEventFilenameFilter) at parse time to build the right strategy once and stash it on the DocumentEventDeclaration; the regex matcher precompiles its pattern in the process so the runtime path stays allocation-free. All concrete strategies compare case-insensitively.