Apache beehive 1.0.2 src

Provides the classes and interfaces fundamental to the NetUI tags. The primary abstract base class is {@link org.apache.beehive.netui.tags.AbstractClassicTag}, which most tags extend from. This class provides implementation of most of the basic services used by the NetUI tags. There are three basic types of NetUI Tags based upon how they data bind to objects:

• Read-only -- These tags bind to their primary value through the value attribute. In addition, many other attributes on tags provide read-only binding.
• Read-Write -- These values provide read/write access to variables on the server. Tags bind their primary value through the dataSource attribute.
• Read-Write Multiple Values -- This type of tag may read and write multiple values. Typically, these tags support a optionsDataSource attribute allowing the full set of options to be specified.

AbstractBaseTag provides base features allowing the implementation of dataSource, defaultValue, and optionsDataSource. There are also base classes in both this package and the {@link org.apache.beehive.netui.tags.html} package which support these attributes.

The primary base classes are:

• AbstractBaseTag -- This is an abstract base class for all tags. I provides support for generic tag features, expression management, naming support, generic attribute support, error reporting and JavaScript services.
• DataSourceTag --
• DefaultableDataSourceTag --
• OptionsDataSourceTag --

There are a number of supporting interfaces provided by the package. These interfaces allow tags to provide services or participate in provided services. These are the primary interfaces:

• DataAccessProvider -- This interfaces allows object to provide their children with a relative binding context using the 'container' binding context.
• ErrorReporter -- This interfaces allows objects to act as a container for reporting errors generated by their children.
• ScriptReporter -- This interfaces allows objects to act as a container for JavaScript for their children.

This package defines the core set of HTML tags provided by NetUI.

The tags used by a template page are:

• HtmlBase -- This is the base abstract type for the HTML specific tags.

This package provides support for plugable naming of data source elements.

The tags used by a template page are:

• NameInterceptor -- This interface defines the contract for the naming service.

This package defines a set of JSP tag extensions providing a simple templating mechanism. A template page is a JSP page defining the overall look and feel of a set of pages. It does this by providing an overall layout structure, style and design of the page and defines placeholders for content. These placeholders are called sections. A content page is a JSP page containing the content. The content page provides the sections of content plugged into the template. Combining the content page and the template page creates the overall look and feel of the content. The big advantage of templates is the ability to change the look and feel of a set of pages without being forced to modify each page.

The NetUI Template tags define two sets of tag extensions. The first set is used by within a JSP template page to define placeholder where content page provides content. The second set of tags is used within a content page to indicate the template to use and to define the content that will be presented within the template.

The tags used by a template page are:

• IncludeSection -- This tag defines a placeholder for content.
• Attribute -- This tag defines an attribute that may be set within the content page.

The tags used by a content page are:

• Section -- This tag contains the content included within a section defined in the template.
• SetAttribute -- This tag defines the value of an attribute used by a template.
• Template -- This tag specifies which template page is being used for the content.

One additional tag is included in the package. The Visible tag defines a section that may be visible or not depending upon a boolean value. The tag may be used either within content or within a template.