Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Migrated to Confluence 5.3

Velocity tags are extensions of the generic Struts Tags provided by WebWorkthe framework. You can get started almost immediately by simply jump right in just by knowing the structure in which the tags can be accessed: #wwxxx #s*tag *(...) ... #end, where xxx tag is any of the Struts Tags supported by WebWork.

Note

As of WebWork 2.2, the use of Velocity for templating internal WebWork UI Tags has been deprecated. Many of the new internal 2.2 UI Tag features were not built for Velocity, and moving forward, support for the legacy internal templates of Velocity Tags may be removed entirely. The new and legacy 2.2 UI tags have been implemented in FreeMarker.

However, support for the Velocity result type as well as the Velocity directives shown below will continue to be supported and developed. By default, WebWork's TemplateEngine will call the FreeMarker UI Tags using the Velocity syntax noted below (through Velocity directives).

See WebWork 2 UI Tag Guide for more information.

...

the framework.

For example, in JSP you might create a form like so:using Struts tags.

Code Block
xml
xml
titleJSP Form
<ww<s:form action="updatePerson">
    <ww<s:textfield label="First name" name="firstName"/>
    <ww<s:submit value="Update"/>
</wws:form>

In Velocity, the same form is built like so:can also be built using macros.

Code Block
xml
xml
titleVM Form
#wwform#sform ("action=updatePerson")
    #wwtextfield#stextfield ("label=First name" "name=firstName")
    #wwsubmit#ssubmit ("value=Update")
#end

Block and Inline Tags

You may notice that some Some VM tags require an #end statement , while others do not. Due to The inconsistency arises from a limitation in Velocity , where tags must declare if they are a block or inline tag up front. As such, by default all tags are inline except for a few key ones, such as the form tag. We strongly encourage you to look at FreeMarker, which provides much better flexibility in this area as well as others.

Back To: Tag Developers Guide