[
https://issues.jboss.org/browse/JBESB-3587?page=com.atlassian.jira.plugin...
]
Jean-Marc Reymond commented on JBESB-3587:
------------------------------------------
Hi,
I tested Eduardo's patch and it works just fine.
Have a look at
http://community.jboss.org/message/594443 for more details regarding how to
configure the action in jboss-esb.xml and how to add the dynamic parameter in your XSL
file.
One thing I did differently though is that I fetch the value of the parameter from the
message body, not via ObjectMapper.
The code in getXslParameters looks like this:
Object fromMessage = message.getBody().get(xslParamLocation);
if (null != fromMessage) {
xslParams.put(xslParam, fromMessage);
}
This could be nicely and easily added to JBoss ESB 4.11... :)
JM.
Enabling xslt parameters support in XsltAction
----------------------------------------------
Key: JBESB-3587
URL:
https://issues.jboss.org/browse/JBESB-3587
Project: JBoss ESB
Issue Type: Enhancement
Security Level: Public(Everyone can see)
Components: Transformation Service
Affects Versions: 4.9
Environment: Linux
Reporter: Eduardo de Vera Toquero
Priority: Minor
Labels: configuration, parameters, xslt:param, xsltAction
Attachments: xslt-param-patch.txt
Original Estimate: 1 week
Remaining Estimate: 1 week
Enhancement of xslt parameters in order to be able to pass values to xslt parameters on
the xslt action. Ideally, using prefixes, one could chose whether to pass a value located
at the configuration file (ConfigTree) or from the ESB Message. Values need to be
stringed.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira