Github user ijokarumawak commented on the issue:
https://github.com/apache/nifi/pull/1450
@mattyb149 Thanks for sharing your use case. That's interesting.
Why does your processor need DBCPService's URL? For provenance? If so, I'd
prefer creating another interface looks like below:
```java
public interface ExternalSource {
String getTransitUri();
}
```
Then add the interface to ControllerServices that interact with external
source such as DBCPService, so that processors use those controller services
can create more meaningful provenance events. For DBCPService,
DatabaseConnectionURL would be legitimate for a return value of getTransitUri
method.
Or, if you need to use the same configuration among ControllerService and
Processor, then VariableRegistry can be helpful.
How do you think?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
