Adds a command to the list of commands to be executed. Note that each command configuration should have at least one execute action, otherwise the tailor will not lead to any command executions.

If the Roo user does not provide a value for an argument with the given name on the shell, this default value will be chosen.

The following configuration defines a chain of commands that will be triggered by the project command, to create a parent project with packaging “pom” with two modules named “projectname-domain” and “projectname-data”.

Note how you can use argument values from the input command as placeholders by using “${argumentname}”.

tailor.xml:

<tailor name="mywebstyle" description="Standards for web projects with 2 modules">
   <config command="project">
      <action type="defaultvalue" argument="packaging" value="pom" />
      <action type="execute" />
      <action type="execute" command="module create --moduleName ${projectName}-domain --topLevelPackage ${topLevelPackage}"/>
      <action type="focus" module="~"/>
      <action type="execute" command="module create --moduleName ${projectName}-web --topLevelPackage ${topLevelPackage} --packaging war"/>
      <action type="focus" module="${projectName}-domain"/>
   </config>
</tailor>

Shell:

tailor activate --name mywebstyle
project --topLevelPackage com.foo.sample --projectName myapp

Will result in:

project --topLevelPackage com.foo.sample --projectName mywebapp --packaging pom
module create --moduleName myapp-domain --topLevelPackage com.foo.sample
module focus --moduleName ~
module create --moduleName myapp-web --topLevelPackage com.foo.sample --packaging war
module focus --moduleName myapp-domain

The following example shows how to tailor the “entity jpa” command with a default value for the "activeRecord" argument, and a default module to put all entities in.

Note that the module name value for the "focus" action is interpreted as "module name contains x". That is why this example works with the project setup described in the previous example, which sets up a module named "${projectName]-domain".

tailor.xml:

<config command="entity jpa">
   <action type="focus" module="domain"/>
   <action type="defaultvalue" argument="--activeRecord" value="false"/>
   <action type="execute"/>
</config>

Shell:

entity jpa --class ~.Customer

Results in:

module focus --moduleName webapp-domain
entity jpa --class ~.Customer --activeRecord false

In this example, the tailor configuration defines a new alias command that will trigger a set of other commands to scaffold repository, service and web layer for an entity. Note that this configuration does not define the "execute" action to execute the original "layer" command.

Although "layer" is not a command known to the shell, it won’t produce an error, because the tailor will transform it into a set of different commands, excluding the original. The downside is that you won’t get command completion support for this alias from the shell.

tailor.xml:

<config command="layer">
   <action type="focus" module="domain"/>
   <!-- Create spring data JPA repository -->
   <action type="execute" command="repository jpa --interface ${entity}Repository --entity ${entity}"/>
   <!-- Create service interface and implementation class-->
   <action type="execute" command="service --interface ${entity}Service --class ${entity}ServiceImpl --entity ${entity}"/>
   <action type="focus" module="web"/>
   <action type="execute" command="web mvc scaffold --class ${entity}Controller --backingType ${entity}"/>
</config>

Shell:

layer --entity ~.Customer

Results in:

module focus --moduleName webapp-domain
repository jpa --interface ~.CustomerRepository --entity ~.Customer
service --interface ~.CustomerService --class ~.CustomerServiceImpl --entity ~.Customer
module focus --moduleName webapp-web
web mvc scaffold --class ~.CustomerController --backingType ~.Customer