[ https://issues.apache.org/jira/browse/NIFI-5073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448457#comment-16448457 ]
Sivaprasanna Sethuraman commented on NIFI-5073: ----------------------------------------------- I think the problem is restricted to just the '_JMSConnectionFactoryProvider_'. Just verified that the `Broker URI` uses a custom validator and it doesn't use `NON_EMPTY_VALIDATOR` and not `NON_EMPTY_EL_VALIDATOR`. I checked with other controller services and the EL resolves fine on them. I'll do quick build and test. If everything works, I'll raise a PR. > Process Group defined "variables" are not being properly used by in scope > controller services > --------------------------------------------------------------------------------------------- > > Key: NIFI-5073 > URL: https://issues.apache.org/jira/browse/NIFI-5073 > Project: Apache NiFi > Issue Type: Bug > Components: Core Framework > Affects Versions: 1.5.0, 1.6.0 > Reporter: Matthew Clarke > Priority: Major > > Create a new process Group. > Add "Variables" to the process group: > for example: > broker_uri=tcp://localhost:4141 > client_libs=/NiFi/custom-lib-dir/MQlib > con_factory=blah > Then while that process group is selected, create a controller service. > Create JMSConnectionFactory. > Configure this controller service to use EL for PG defined variables above: > ${con_factory}, ${con_factory}, and ${broker_uri} > The controller service will remain invalid because the EL statements are not > properly resolved to their set values. > Doing the exact same thing above using the external NiFi registry file works > as expected. -- This message was sent by Atlassian JIRA (v7.6.3#76005)