AbstractResourceOrigin.AbstractResource simply delegates to.Predicates.alwaysTrue(), avoids verbose type parameter declaration and provides a (debatably) better name.classpath entries mapped to their absolute paths on the basis of classpath configuration
and some classpath traversal strategy.ClasspathEntriesResolver based Reflections library's VFS.Resource for ClasspathResourceOrigin.ResourceOrigin which serves resources collected from the web application classpath.ClasspathEntry objects and
provides convenient access to it.ClasspathEntry by a path fails.ClasspathService.ClasspathService.classpath service configurations aggregated in one place.ClasspathServiceConfiguration objects.@Inject ResourceOrigin in their code.ResourceOriginFactory about why we can't use @Multibinding at the moment.ClasspathFile implementation oriented onto development application mode.Classpath service implementation which targets
development application mode.classpath resource changes communication.DirectoryWatcher covers implementation of the low level WatchService API.DirectoryWatcher.DirectoryWatcher(boolean, boolean, MagnoliaConfigurationProperties) instead.DirectoryWatcherService.DirectoryWatcherService(MagnoliaConfigurationProperties) instead.PredicatedResourceVisitor which simply "collects" file resources matching a given pattern.Resource for FileSystemResourceOrigin.ResourceOrigin which loads resources on the file system.Function, Predicate and Comparator implementations that are useful when working with ResourceOrigin and Resource, and some more useful ones that had no better place for now.Resource object based on the given path.LayeredResourceOrigin.openReader(LayeredResource),
this method used in AbstractResourceOrigin.openReader(info.magnolia.resourceloader.AbstractResource)
should never be called.service.directory.classpath entry corresponding to a given path.classpath entry.Predicate which would based on the given classpath resource path deduce whether that is
actually a meaningful resource.Resource for this origin's declared root.entry
which corresponds to a given path.Resource for JcrResourceOrigin.ResourceOrigin which loads resources from JCR.Resource for LayeredResourceOrigin.ResourceOrigin which aggregates
other instances of ResourceOrigin; resources located on the same path will
be served from the foremost ResourceOrigin, but resources that exist only on one path will always be served.ProductionModeClasspathFile which maps the legacy (pre-5.4) classpath resource locations to the new logic
by means of relaying the /mgnl-resources prefixed classpath resources to paths without such prefix.Classpath resource origin which hosts
the pre-5.4 classpath resources (from the /mgnl-resources prefixed locations).ResourceVisitor which logs the files and directories it traverses, then simply delegate to another given visitor.ClasspathService variation which monitors the changes of classpath resources and communicates those to the
subscribers.Predicates.alwaysFalse(), avoids verbose type parameter declaration, and provides a (debatably) better name.Resource out of a relative path.Function to all files, according to applyToFile.Reader for this resource; if the associated ResourceOrigin can guess it, this will have been
opened with the corrected encoding.InputStream for this resource.origin's root path and normalize it.Resource's handle matches the given pattern.WatchEvent as needed.ClasspathFile implementation oriented onto production application mode.Classpath service implementation which targets
production application mode.DirectoryWatcher, with given filtering predicate and callback.handler.classpath enty mappings bound to the classpath configuration.ResourceOrigins.resource origin and
get notified of the resource related events via ResourceOriginChange objects.ResourceChangeHandler registration in an ResourceOrigin.resource related change.ResourceOriginChange.resource change types.ResourceOrigin.registerResourceChangeHandler(ResourceChangeHandler) allows for registering more sophisticated
resource change handlers rendering this class obsolete.Resource.ResourceOrigin.traverseWith(ResourceVisitor) to visit resources.ResourceVisitor.URLConnection.ResourceVisitor.visitDirectory(Resource) is
NOT called for files.Function whose target type is Void, e.g avoids having to declare
the Void type parameter having to explicitly return null in implements.DirectoryWatcher's own callback interface for typical WatchEvent kinds.AbstractResourceOrigin.registerResourceChangeHandler(ResourceChangeHandler) instead. See ResourceOrigin.watchForChanges(ResourceVisitor) JavaDoc for more detailsResourceOrigin.registerResourceChangeHandler(ResourceChangeHandler) instead. Current method is less preferable to
be used for resource changes monitoring because ResourceVisitor is not a suitable interface to communicate such changes. E.g. ResourceVisitor
has no API to provide the context of the change (which ResourceOrigin the change has happened at, what was the type of the change etc). Also ResourceVisitor requires
an instance of Resource - it is not usable to communicate deletion of resources.Function to everything.visitAndApply predicate and applies the given Function according to visitAndApply.visitDirectory predicate and applies the given Function according to applyFunction.visitDirectory predicate and applies the given Function according to applyToDirectory and applyToFile depending on the resource's type.Copyright © 2003–2018 Magnolia International Ltd.. All rights reserved.