[
https://issues.apache.org/jira/browse/NIFI-4130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16083571#comment-16083571
]
ASF GitHub Bot commented on NIFI-4130:
--------------------------------------
Github user pvillard31 commented on the issue:
https://github.com/apache/nifi/pull/1953
Yes @jfrazee, that could be an option. However, do you think that's a good
idea to have the XSLT as an attribute of the flow files? The XSLT could be
really big and I'm not sure users will have the reflex to use an
UpdateAttribute to remove it after the TransformXml.
> TransformXml - provide a way to define XSLT without external files
> ------------------------------------------------------------------
>
> Key: NIFI-4130
> URL: https://issues.apache.org/jira/browse/NIFI-4130
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Reporter: Pierre Villard
> Assignee: Pierre Villard
>
> In cluster deployments the need to reference external configuration files can
> be annoying since it requires to access to all the NiFi nodes and to
> correctly deploy the files. It would be interesting to leverage the lookup
> controller services in TransformXml to provide a way to define XSLT directly
> from the UI without external configuration files.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
