[
https://issues.apache.org/jira/browse/NIFI-6190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16812681#comment-16812681
]
Ed R edited comment on NIFI-6190 at 4/8/19 6:17 PM:
----------------------------------------------------
Ah, thanks, that did solve my problem. (Specifically, including that dependency
using the posted xml; I already was using the Maven plug-in.) Closing this
issue.
was (Author: edr):
Ah, thanks, that did solve my problem. Closed.
> identifiesControllerService does not work when not inheriting from nar-bundles
> ------------------------------------------------------------------------------
>
> Key: NIFI-6190
> URL: https://issues.apache.org/jira/browse/NIFI-6190
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Reporter: Ed R
> Priority: Major
>
> My company requires that we inherit from our standard parent pom, so our
> custom NiFi processors just bring in the required NiFi components as
> dependencies. This works fine, except that we cannot integrate with
> controller services.
> When we have a property that uses identifiesControllerService(), NiFi
> attempts to find that controller in the custom processor's package and
> version, and not the package/version of the class passed to that method.
> So if the custom processor is in package "com.company.product" with version
> 1.0-SNAPSHOT, and it pulls in NiFi 1.8.0 components like
> DistributedMapCacheClient, the processor builds just fine of course, but when
> trying to configure an instance of the processor in NiFi's UI, it is unable
> to find or create any instances of the controller service for that processor
> because it says it can't find com.company.product.DistributedMapCacheClient
> 1.0-SNAPSHOT.
> I even tried calling
> context.getControllerServiceLookup().getControllerServiceIdentifiers(DistributedMapCacheClient.class)
> and it returns an empty set.
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
