With Orchestrator, you can create custom Tapestry Web view components to perform orchestration functions from Web pages. A Tapestry Web view component conforms to the Tapestry Framework standard version 4.0.

A Tapestry Web view component must contain a component specification file and a component template.


The Tapestry component template file and the component specification must have the same name. For example, if you name a component template MyComponent.html, you must name the associated component specification MyComponent.jwc. Web view components that you use in different Web views that run in the same server must have unique names.

You must save the component files in the components folder in the Web view file structure. If you create subfolders in the components folder, you must specify the full path to a component when you set the jwcid attribute in HTML pages. For example, if you include a MyBorder component in a <WebView_Folder>\components\layout\ subfolder, you must set the jwcid attribute, as the following example shows:

<div jwcid="@layout/MyBorder">

You can precede the @ character with a unique identifier. With the unique identifier, you can reuse the class throughout the HTML page, by referencing the unique identifier.

In the following example, the component is Border and the unique identifier is myBorderComponent.

<div jwcid="myBorderComponent@MyBorder">