
150 vFoglight
Web Component Guide
Tasks
Tasks are logical actions external to Web Component Framework. Examples in the
vFoglight regime are tasks for clearing and acknowledging alarms, building a service,
scheduling a report, or launching PerformaSure in context on a particular request.
Otherwise tasks are configured to behave in the flow in the same manner as views.
The workflow generally looks like:
• Action on a View
• Invoke component
• Update page
Some tasks may break the flow – that is, not return. An example of this is launching
PerformaSure. In this case the task does not have a flow action that can be configured to
update the page.
A task consists of its code and three text files, and is usually packaged in a JAR file.
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.
Note You can use the Execute Groovy Task component to implement a simple task. See the Web
Component Tutorial for an example.
Components of a Web Component Framework Task
descriptor.xml Location of the code for the task and its characteristics.
types.xml Configuration schema: the task’s properties.
strings.properties The English text for the component. This provides a default
localization. Other localization files have names like
strings_fr.properties.
Kommentare zu diesen Handbüchern