Nav

Parse Template Reference

Parse Template is the Mule component to use for processing a template and obtaining a result. A template is defined as text with embedded Mule expressions that are evaluated and replaced with their result.

You can configure template through an external file reference, or you can embed it in the component definition itself.

Configuring a Parse Template

  1. In Studio, drag a Parse Template message processor from the palette onto the canvas.

  2. Configure the fields described in this table:

parse

+

Field Value Description

Content

Template String

A string to use as a template. Instead of defining the template in an external file, you can use this field to write it inline. It can contain embedded expressions to be evaluated and replaced with their results.

Display Name

Parse Template

Customize to display a unique name for the transformer in your application.

Location

filepath

Define the location of the file that Mule uses as a template into which to insert values extracted from the message properties or variables.

Target Variable

Variable Name

The name of a variable where to store the result of evaluating the expression defined in Target Value.

Target Value

Expression

Mule Expression to be evaluated after executing the Parse Template and which result is stored in a variable with name as defined in the Target Variable field.

If you are using the XML editor in Studio or a Standalone Mule instance:

  • Add a parse-template element to your flow, then configure according to the tables below.

    <parse-template location="users/administrator/desktop/hrweb/confirmation.html" doc:name="Parse Template"/>

Attributes of the parse-template element:

Element Attributes Value

content

A string representing the template to be used where the embedded expressions will be evaluated and replaced by their results.

location

Filepath which defines the location of the file that Mule uses as a template into which to insert values extracted from the message properties or variables.

doc:name

Customize to display a unique name for the transformer in your application. (Note: Not needed in Mule standalone.)

target

The name of a variable where the result of the expression defined in targetValue will be stored after the Parse Template is executed.

targetValue

A Mule Expression that will be evaluated after the Parse Template is executed and which result will be stored in a variable with name as defined in the target attribute.

Code Example

The following example demonstrates the use of a Parse Template in an application which accepts queries by employeeID in order to acquire data about an employee.  

In this case, the Parse Template uses a flow-external file as a template into which it inserts values for fields – name, department, job title, start date, and employee type – drawn from the message payload. The flow then returns the template-built payload to the caller. 

parse-template-flow


         
      
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
<?xml version="1.0" encoding="UTF-8"?>

<mule xmlns:ee="http://www.mulesoft.org/schema/mule/ee/core" xmlns:http="http://www.mulesoft.org/schema/mule/http"
      xmlns:db="http://www.mulesoft.org/schema/mule/db"
      xmlns="http://www.mulesoft.org/schema/mule/core" xmlns:doc="http://www.mulesoft.org/schema/mule/documentation" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/current/mule.xsd
http://www.mulesoft.org/schema/mule/db http://www.mulesoft.org/schema/mule/db/current/mule-db.xsd
http://www.mulesoft.org/schema/mule/http http://www.mulesoft.org/schema/mule/http/current/mule-http.xsd
http://www.mulesoft.org/schema/mule/ee/core http://www.mulesoft.org/schema/mule/ee/core/current/mule-ee.xsd">
    <db:config name="Database_Config" doc:name="Database Config" doc:id="e4df87d8-ec1e-49ec-a528-43e93baa5bda" >
        <db:my-sql-connection host="localhost" port="3306" user="user" password="pw" database="MySQL_Data_Source" />
    </db:config>
    <http:listener-config name="HTTP_Listener_config" doc:name="HTTP Listener config" doc:id="724690b1-cc2f-451a-86eb-66f7750feba1">
        <http:listener-connection host="localhost" port="8081" />
    </http:listener-config>
    <flow name="exampleTemplateFlow1" doc:id="b8cc9464-5991-4977-978f-9f51eb252ec8" >
        <http:listener doc:name="Listener" doc:id="f334ba27-ae1f-4da5-a194-26e57a1aa637" config-ref="HTTP_Listener_config" path="/getEmployee"/>
        <db:select doc:name="Select" doc:id="c3ab7830-9920-4637-9329-954a8a94e54c" config-ref="Database_Config">
            <ee:repeatable-file-store-iterable />
            <db:sql >SELECT * FROM Employees WHERE id=#[attributes.queryParams['id']]</db:sql>
        </db:select>
        <parse-template doc:name="Parse Template" doc:id="53211517-f943-40b2-86e3-20a0e1ca4eb6" location="src/main/resources/responseHtml.template"/>
    </flow>
</mule>

To use the application in this example, you must send an HTTP request with a URL that includes an ID query parameter, such as `http://localhost:8081/getEmployee?id=12345`.

See Also