All Classes and Interfaces

Class
Description
 
 
 
 
 
 
 
 
 
A classpath-based TemplateResolver.
 
 
 
Registers a route for the ComponentDeclarationsView when Vaadin is NOT running in production mode.
 
Component factories are responsible for creating components based on HTML elements parsed from a template.
Post-processors can make additional modifications to components created by a factory; this is useful e.g. to handle mix-in interfaces like HasSize.
 
 
 
 
 
 
 
 
 
Describes a Component or mix-in interface and how it is represented in a DUI template via its tag and/or attributes.
Container for repeated @DuiComponent annotations.
 
 
 
Used to annotate fragment hosts (i.e. template hosts of fragments).
Abstract base class for composites whose content is created from a template fragment.
Abstract base class for fields whose content is created from a template fragment.
 
 
 
 
 
 
 
A generic handler for HasComponents that will only be used as a last resort.
 
 
 
 
 
 
 
Handles the "class" and "style" attributes on all components.
 
Handles the "theme" attribute on all components.
 
 
 
 
 
 
 
Used to mark fields to which components from the template should be mapped.
 
 
 
 
Contains the end result of parsing and processing a template, including the root component and information about the encountered components, slots and fragments.
 
 
 
 
 
 
Used to mark fields that should be inserted into a <slot> in the template.
 
 
 
Used to annotate template hosts.
 
Abstract base class for composites whose content is created from a template.
Abstract base class for dialogs whose content is created from a template.
 
 
The TemplateEngine is responsible for instantiating DUI templates, as well as perform the associated component mapping and slotting on template hosts.
The cache mode for templates.
 
Abstract base class for fields whose content is created from a template.
Gathers the state while parsing a template and provides methods to parse attributes and child components.
 
 
 
Registers components involved in the processing of DUI templates.
A registry of components involved in the processing of DUI templates.
Configuration properties for TemplateAutoConfiguration.
The TemplateReport contains errors and warning that occurred while instantiating or validating a DUI template.
 
 
Template resolvers are responsible for loading templates based on a provided template ID and return them as Document.
Used as dummy component when a template slot is otherwise empty.