public final class LibraryMapping extends ObjectUsed to configure the
ComponentClassResolver, to allow it to map library names to library root packages (the application namespace is a special case of this). In each case, a prefix on the path is mapped to a package. The root package name should have a number of sub-packages:
- contains named pages
- contains components
- contains component mixins
- contains base classes
- See Also:
All Methods Instance Methods Concrete Methods Deprecated Methods Modifier and Type Method Description
getPathPrefix()Deprecated.In 5.4, use
public LibraryMapping(String libraryName, String rootPackage)Identifies the root package of a library. The application has uses the library name "" (the empty string). The special library "core" is all the built-in components. The library name is sometimes referred to as the "path prefix" or the "virtual folder name". This is for historical reasons, as the concept of a library and how it was defined and managed evolved from release to release. The library name should be alpha numeric, and directly encodable into a URL. It may contain slashes (though this is not used often), but may not start or end with one. Note that it is allowed to contribute multiple LibraryMappings with the library name to the
ComponentClassResolver, and the results are merged: the single library will have multiple root packages. Be careful that none of the root packages overlap!
libraryName- the unique identifier for the library.
rootPackage- the root package to search for classes; sub-packages will include ".pages", ".components", etc.
public String getPathPrefix()Deprecated.In 5.4, use
libraryNameinstead.Returns the library name; the method is oddly named for historical reasons. The library name is sometimes referred to as the virtual folder name.