APIs to evaluate content with Velocity

Description

This module offers APIs to evaluate content with Velocity.

The following concepts are exposed:

• VelocityEngine: This is the object on which you call evaluate()
• VelocityConfiguration: Default Velocity configuration. Sets default configuration parameters and default tools (see below)
• VelocityContextFactory: Allows to create Velocity Context. Context are used when evaluating in order to expose some variable to the script content
• VelocityFactory: Allows to create several VelocityEngine based on a key you defined. For example XWiki Platform uses this to have one VelocityEngine per Skin. This allows each Skin to provide its own set of Velocimacros.
• VelocityContextInitializer: Allows to callback components that implements this Role when VelocityFactory is called to create a new Velocity Context. This allows your code to automatically bind new variables in the Velocity Context.

To see more of the API read the Velocity Module Javadoc

Velocity Tools

For security reasons we're not exposing some APIs to Velocity scripting (such as Reflection or Threading APIs). In addition Velocity is a template language and doesn't have the full support a complete development language has (for example you cannot instantiate new classes or you cannot handle exceptions just to name 2). Thus we need to offer some Tools (i.e. API) that are meant to be used from Velocity to make it easy to create powerful scripts in Velocity code.

The following Velocity tools are made available:

• Collections Tool: $collectionstool (since 4.0M1)
• Comparison Date Tool (extends the standard Velocity Comparison Date Tool, which in turn extends the Date Tool): $datetool
• Escape Tool (extends the standard Velocity escape tool): $escapetool (since 2.7RC1)
• JSON Tool: $jsontool (since 4.0M2)
• List Tool: $listtool (deprecated; any methods provided by this tool can be used directly on arrays and lists now)
• Math Tool: $mathtool
• Message Tool: $msg This tool is used to provide internationalized messages based on keys. For more details see the How to Write Internationalized Applications tutorial.
• Number Tool: $numbertool
• Regex Tool: $regextool (since 2.0RC2)
• Sort Tool: $sorttool
• String Tool
  • String Tool: $stringtool (since 6.3M1)
  • String Tool: $stringtool (since 3.4M1)
• URL Tool: $urltool allows to parse URL's; currently only a parseQuery method is supported to parse the query string of a given URL (since 6.3M1)
• Exception Tool: $exceptiontool provides useful helpers to manipulate exceptions (get root cause, transform into a String, etc) (since 6.3M1)
• NIO Tool: $niotool allows to use some non-dangerous NIO2 API from Velocity (since 7.4M2). Useful along with the VFS API.

See more available variables at XWiki Scripting Reference Documentation

Velocity Uberspectors

The introspection behaviour in Velocity can be customized by implementing an uberspector. Velocity supports by default only one uberspector. To overcome this limitation we have implemented an uberspector that forwards all calls to a chain of uberspectors.

Method Arguments Uberspector

A chainable uberspector that tries to convert method arguments to formal parameter types when the passed arguments don't match the method signature. In other words, it looks for a method matching the passed arguments and if none is found then it tries the convert the arguments to match the available method signatures (the available methods with the same name and the same number of parameters but with different parameter types). E.g.:

But this is not limited to enums. The conversion is done using the Properties Module which means you can create and register custom converters for data types specific to your application domain.

XWiki 7.4.3/8.1M1 This uberspector supports calling varargs methods. For example, if you have the following Java method public boolean isRegularFile(Path path, LinkOption... options) that is bound through $niotool, then you can call it with $niotool.isRegularFile("path/to/a/file").

Velocity Directives

XWiki provides a Velocity Directive to catch Exceptions from Velocity.

For example:

Starting with XWiki 8.3M2/7.4.5/8.1.2, it's possible to name the Velocity variable in which the exception will be saved. For example:

Prerequisites & Installation Instructions

We recommend using the Extension Manager to install this extension (Make sure that the text "Installable with the Extension Manager" is displayed at the top right location on this page to know if this extension can be installed with the Extension Manager). Note that installing Extensions when being offline is currently not supported and you'd need to use some complex manual method.

You can also use the manual method which involves dropping the JAR file and all its dependencies into the WEB-INF/lib folder and restarting XWiki.

Dependencies

Dependencies for this extension (org.xwiki.commons:xwiki-commons-velocity 10.7):

• org.xwiki.commons:xwiki-commons-component-api 10.7
• org.xwiki.commons:xwiki-commons-configuration-api 10.7
• org.xwiki.commons:xwiki-commons-script 10.7
• org.xwiki.commons:xwiki-commons-xml 10.7
• org.xwiki.commons:xwiki-commons-management 10.7
• org.xwiki.commons:xwiki-commons-properties 10.7
• org.apache.velocity:velocity 1.7
• org.apache.velocity:velocity-tools 2.0
• org.apache.commons:commons-lang3 3.7
• org.apache.commons:commons-collections4 4.1
• org.apache.commons:commons-text 1.4
• commons-codec:commons-codec 1.11
• com.fasterxml.jackson.core:jackson-core 2.9.6
• com.fasterxml.jackson.core:jackson-databind 2.9.6
• net.sf.json-lib:json-lib:jdk15 2.4
• com.tdunning:json 1.8
• org.apache.httpcomponents:httpclient 4.5.5