It is even possible to nest dynamic values. In our examples this makes sense as we can combine the both processors that we are now familiar with and replace the fixed date with the current date that the system processor offers:
...
<step id="compose" processor="hello">
<load parameter="username">
<value processor=”dateFormatter” result=”output”>
<value processor="system" result="currentDate"/>
</value>
</load>
...If we upload this and reload the page, we will see the current date in a much more beautiful representation than we know it from our past examples!
Note
Try to avoid nesting dynamic values deeply as this makes your process definition harder to understand.
If you take a sharp look at the both usages of the value tag that we know right now, it might come into your mind to combine these. It is possible to load the result of a processor that gets feed with a stored value as input. As an example we want to use a parameter that is encoded into the URL as the date to format. This can be done either by nesting dynamic values…
<step id="compose" processor="hello">
<load parameter="username">
<value processor=”dateFormatter” result=”output”>
<value store=”request-parameter" key="date"/>
</value>
</load>
...…or by using a more compact syntax:
...
<step id="compose" processor="hello">
<load parameter="username">
<value processor=”dateFormatter” result=”output”
store=”request-parameter" key="date"/>
</value>
</load>
...In both cases the result looks identically:
