MULE-6501 - Handle XSLT parameters with expressions that return (XML) objects#8
MULE-6501 - Handle XSLT parameters with expressions that return (XML) objects#8robvalk wants to merge 2 commits intomulesoft:mule-3.xfrom
Conversation
(possibly XML node) objects. Key use-case now supported is extracting a fragment of an XML payload via an #[xpath()] expression, and later using this as a input parameter to an XSLTTransformer. 1. XsltTransformer calls ExpressionManager.evaluate() instead of ExpressionManager.parse() 2. Converts the returned object to a javax.xml.transform.Source if it is convertible. 2a. XMLUtils.toXMLSource() handles conversion of Dom4j nodes as well as complete documents. 3. Otherwise uses the expression result object as-is for the XSLT parameter. The expanded support for Dom4j nodes is because the xpath() function might return a w3c DOM or Dom4j node depending on what format the message payload was in. Converting the XSLT parameter to java.xml.transform.Source allows Saxon to process an XML node parameter as intended.
There was a problem hiding this comment.
Looks like your IDE is using tabs here, use whitespaces and the correct indentation please.
There was a problem hiding this comment.
use stringValue as per mule style guide
|
Hello @robvalk, Thank you very much for your contribution! Thanks again. |
|
Hi @robvalk, I'm planning to close this PR due to inactivity in 15 days. I'm going to leave the issue open and link the PR to not to loose your contributed code. If you prefer to not to have it closed, please don't hesitate to contact. |
|
Hi @robvalk, I'm closing this now. Thanks for your interest in the project. We would love to hear from you again. Feel free to reopen if you want to keep working on this. Regards. |
MULE-6501 - Handle XSLT parameters with expressions that return (possibly XML node) objects.
Key use-case now supported is extracting a fragment of an XML payload
via an #[xpath()] expression, and later using this as a input parameter
to an XSLTTransformer.
ExpressionManager.parse()
convertible.
as complete documents.
parameter.
The expanded support for Dom4j nodes is because the xpath() function
might return a w3c DOM or Dom4j node depending on what format the
message payload was in. Converting the XSLT parameter to
java.xml.transform.Source allows Saxon to process an XML node parameter
as intended.