The Web Component Framework has a concept of renderers for bindings, which can be used to format the output from the binding in various ways. Definitions for all of the renderers are held in a one-file-per-wcf.xml file and in a global file that is common to the whole application. The files are named renderers.xml.
The ID attribute is a unique name that is associated with the corresponding renderer. This is the value that is to be specified in the renderer ID of the binding. See Data .
The optional <associations> section specifies associations between the renderer and sdo types, metric, classes or units, depending on the tags it contains. Each of the tags in the associations section is optional and more than one association of each type may be specified. These associations are used to resolve the renderer when a binding is rendered.
The <configuration> section can be any of the types of configuration mentioned previously. However, each specific class of renderer expects a specific type of configuration.
Otherwise tasks are configured to behave in the flow in the same manner as views.
The workflow generally looks like:
A task consists of its code and three text files, and is usually packaged in a JAR file.
The English text for the component. This provides a default localization. Other localization files have names like strings_fr.properties. |
Tasks are located in META-INF/wcf-metadata/task/X.Y, where X.Y is the Web Component Framework internally generated name for the component.
© ALL RIGHTS RESERVED. Nutzungsbedingungen Datenschutz Cookie Preference Center