[
https://issues.apache.org/jira/browse/NIFI-5232?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17583771#comment-17583771
]
David Handermann commented on NIFI-5232:
----------------------------------------
Thanks for following up on this [~mike.thomsen]! The {{nifi-scripting-nar}}
depends on {{{}nifi-standard-services-api-nar{}}}, so scripted components
should be able to leverage the new service with the
{{WebClientServiceProvider}} interface bundled as a standard Controller Service.
> HttpConnectionService controller service
> ----------------------------------------
>
> Key: NIFI-5232
> URL: https://issues.apache.org/jira/browse/NIFI-5232
> Project: Apache NiFi
> Issue Type: New Feature
> Reporter: Mike Thomsen
> Priority: Major
>
> The functionality of InvokeHttp and related processors should be copied over
> to a controller service that can do much the same thing. This controller
> service would be able to handle all of the common scenarios with HTTP
> connections from processors going forward.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
