[
https://issues.apache.org/jira/browse/NIFI-2574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421635#comment-15421635
]
Andy LoPresto commented on NIFI-2574:
-------------------------------------
We also would like to prevent changing the property values, so the object
should be immutable. I believe the plan is as follows:
{{NiFiProperties}} becomes an {{interface}}
* it has all the static strings for key access
* it has a {{#getProperty(String key)}} which returns a {{String}} value
(potentially {{Object}}?)
{{StandardNiFiProperties}} implements {{NiFiProperties}}
* it has an internal {{Properties}} instance
* it does not have a {{#setProperty()}} method
{{NiFiProperties}} stays in the *nifi-properties* module
{{StandardNiFiProperties}} moves to *nifi-framework-core* module
{{NiFiPropertiesLoader}} is there as well. This class handles instantiation,
file-retrieval, unprotection/decryption, etc. and makes the instance available
to the various contexts.
> Update NiFiProperties usage to a context based accessor rather than static
> singleton
> ------------------------------------------------------------------------------------
>
> Key: NIFI-2574
> URL: https://issues.apache.org/jira/browse/NIFI-2574
> Project: Apache NiFi
> Issue Type: Sub-task
> Components: Configuration, Core Framework
> Reporter: Joseph Witt
> Assignee: Joseph Witt
> Fix For: 1.0.0
>
>
> This is a key step to move our longstanding odd static singleton usage of
> NiFiProperties which enables a loader to exist which will encapsulate all
> logic for dealing with encrypted properties as is the goal of the parent task.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
