Widget architecture

For each widget, there is a <widgetName> directory located in: <DATADIR>/webapps/360-mashup-ui/WEB-INF/jsp/widgets

Each widget has at least two files:

• widget.xml

  The manifest, describing the widget and its options (used by the Administration Console).

• widget.jsp

  The actual widget logic, using JSP.

The Tag Library Descriptors (TLD) documentation is available in the following directory: <INSTALLDIR>/sdk/java-mashupui/project/doc/tld

Tip: If you have installed the Eclipse Plugin, you can open these TLDs from the Project Explorer panel. Right-click MashupUI and select CloudView Mashup > Open tag libraries documentation.

The Widget Reference documentation, which lists all available predefined widgets, is available in: <INSTALLDIR>/sdk/java-mashupui/project/doc/widget-reference/index.html

Tip: If you have installed the Eclipse Plugin, you can open the widget reference documentation from the Project Explorer panel. Right-click MashupUI and select CloudView Mashup > Open widgets documentation.

A Widget can also contain resources such as images, JavaScript, CSS and so on. These resources must be located in sub-folders of the widget directory, for example:

• images/
  • test-image.png
• css/
  • style.css
• js/
  • script.js

Theses resources can be accessed through a conventional URL:

http://<HOSTNAME>:<BASEPORT>/<CONTEXT PATH>/resources/widgets/<widgetName>/<sub-directory>/<resourcename.ext>

Example:

http://localhost:10000/mashup-ui/resources/widgets/myWidget/images/test-image.png

You can refer to them in your widget JSP code with a relative path, using the tag <wh:resource path="path/to/resource" />

Example:

<wh:resource path="images/test-image.png" />

The <widgetName>/lib/ directory can contain a set of packaged JAR files. For example, you can add the jar of a controller under:

• myWidget/

  • lib/

    myController.jar