13.3.12. SmooksTransformer
Important
| Class | org.jboss.soa.esb.actions.converters.SmooksTransformer |
Table 13.7. SmooksTransformer Resource Configuration
| Property | Description | Required |
|---|---|---|
| resource-config |
The
Smooks resource configuration file.
| Yes |
Table 13.8. SmooksTransformer Message Profile Properties (Optional)
| Property | Description | Required |
|---|---|---|
| from |
Message Exchange Participant name. Message Producer.
| No |
| from-type |
Message type/format produced by the "from" message exchange participant.
| No |
| to |
Message Exchange Participant name. Message Consumer.
| No |
| to |
Message Exchange Participant name. Message Consumer.
| No |
| to-type |
Message type/format consumed by the “to” message exchange participant.
| No |
Message.Properties class).
Example 13.7. Sample Configuration: Default Input/Output
<action name="transform" class="org.jboss.soa.esb.actions.converters.SmooksTransformer">
<property name="resource-config" value="/smooks/config-01.xml" />
</action>Example 13.8. Sample Configuration: Named Input/Output
<action name="transform" class="org.jboss.soa.esb.actions.converters.SmooksTransformer">
<property name="resource-config" value="/smooks/config-01.xml" />
<property name="get-payload-location" value="get-order-params" />
<property name="set-payload-location" value="get-order-response" />
</action>Example 13.9. Sample Configuration: Using Message Proiles
<action name="transform" class="org.jboss.soa.esb.actions.converters.SmooksTransformer">
<property name="resource-config" value="/smooks/config-01.xml" />
<property name="from" value="DVDStore:OrderDispatchService" />
<property name="from-type" value="text/xml:fullFillOrder" />
<property name="to" value="DVDWarehouse_1:OrderHandlingService" />
<property name="to-type" value="text/xml:shipOrder" />
</action>Message.Body under their beanId.

Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.