Call Functionality, no Body
This is probably the simplest example: just collect attributes and call into some action. The
only action involved is
, and in this case it should have no body. I.e something like:
In this case we would define a
tag handler that extends
method would take the attribute information,
perhaps interact with the
data and invoke into the appropriate functionality.
The entry for this tag in the Tag Library Descriptor should indicate that the action must have
no body; no
class is needed.
Call Functionality, No Body, Define Object
In a simple variation of the previous example the action defines an object.
After this, an object with name
is available to the scripting language.
The semantics of
invocation is as before except that additionally it should
insert the appropriate object for the mybar entry into the pageContext.
The Tag Library Descriptor entry for this action needs to mention a
that will be used to determine the scripting variables that will be created by the action; in this
case mybar (note that id must be a translation time attribute).
Call Functionality, Define Object by Scope
In some cases, the previous example can also be described without using a TagExtraInfo by
having the bar action enclose the actions that would use the created object. In this case, the
defining action needs not indicate any id attribute but it must have a body:
The nesting actions will invoke
to locate the bar handler
There are a number of template mechanisms in server side frameworks. The simplest of
these mechanisms will take a token and replace it by some fixed replacement text (that can
be changed easily); more sophisticated mechanisms compute the replacement text, and can