Red Hat Docs  >  Manuals  >  Red Hat Web Application Framework  > 

Red Hat Web Application Framework Developer Guide
PrevChapter 4. PresentationNext

Appendix A: Bebop Tag Library Reference Guide

This document is under construction.

Bebop/JSP tag library reference

TagDescription
<show:page [pageClass=...] [pmClass=...] [master=...]> ... </bebop:page>sets up a Bebop page for use in the JSP. Page is specified by class name (pageClass). The pageClass options is omitted if the page is set up in the same JSP (by including a page-definition JSP) or within a master page. The resulting XML produced by the JSP is then displayed by the presentation manager class specified by pmClass (default BasePresentationManager)
<show:component name=... />Shows a component from the Bebop page in the JSP. There is no need for more specific tags for each component here. The component is displayed with default global styling.
<show:form name=...> ... </show:form>Shows a form from the Bebop page in the JSP. If the form tag contains a body, it is not displayed with the default global styling though the <form> tag and page state (input type=hidden...) will be preserved. If the tag body is empty, though, the entire form will be displayed with default styling.
<show:list name=...> ... <show:listItem/> ... </show:list>Shows the contents of a model-backed List from Bebop page in the JSP. The body of the tag will be displayed for each item of the list, so this tag is effectively a loop. The list itself is not displayed with the default global styling though the individual list items contained within will be where indicated by <show:listItem/>. Like with show:form, if the tag body is empty, the entire list will be displayed with default styling.
<show:slave/>Includes the contents of the slave page in this point in the master page.

Table 4-1. Tags available for displaying Bebop components

Available page definition tags

Please see the note in the previous section about the experimental nature of these tags.

TagDescription
<define:page name="..." title="..." [pageClass="..."]

The define:page tag is the top-level tag for Bebop-JSP integration, and so it is responsible for several processing actions:

  • Declares a Bebop Page object

  • Generates an XML document from Bebop

  • Puts this XML document into the request attributes for the show:page tags

"name" is the name of the pageContext attribute that refers to the Bebop page. The optional "pageClass" attribute is the name of the Page class that will be used as the base class for the created page.

<define:image [name=...] src=... [height=...] [width=...] [alt=...] [border=...]/> Creates an Image object at this point in the page.
<define:link [name=...] url=.../> Creates an Link object at this point in the page.
<define:form name=... [method=...] [action=...] [encType=...]> The define:form tag indicates that a Bebop form should be created at this particular location in the page.
<define:text name=... [size=...] [maxLength=...] [type=...]/> Creates a TextField at this particular location in the page.
<define:textArea name=... [rows=...] [cols=...] [wrap="nowrap|soft|hard"]/> Creates a TextArea at this particular location in the page.
<define:submit name=... [label=...] [bundle=...]/> Creates a form submit button at this particular location in the page, with an optional specified label. If a resource bundle is specified the label is used as a key.
<define:radioGroup name=...> Creates a radio group. Must be enclosed within a form.
<define:checkboxGroup name=... [vertical="true"]> Creates a checkbox group. Must be enclosed within a form. Checkboxes are arranged horizontally by default, but can be arranged vertically with the vertical attribute.
<define:select name=...> Creates a selection widget. Must be enclosed within a form.
<define:multipleSelect name=...> Creates a multi-selection widget. Must be enclosed within a form.
<define:option name=... [value=...] [selected=...] [bundle=...] /> defines an option within a select widget or checkbox/radio group.
<define:component classname=...> Creates a component of the given class and adds it at the current location in the page. Requires that the component class have a no-argument constructor.

Table 4-2. Tags available for defining Bebop components

Note that if a JSP tag does not exist for adding a particular component to a page, it is trivial to create. As a last resort, you can use the generic define:component tag, if the class has a no-argument constructor. It is also trivial to escape into Java from a JSP and create a component object explicitly in a Java scriptlet: 
<define:page name="p" title="page title">
  <% 
    MyComponent c = new MyComponent();
    p.add(c);
  %>
</define:page>

PrevHomeNext
UpAppendix B: Notes JSP Walkthrough