[
https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432905#comment-15432905
]
Marshall Schor commented on UIMA-5043:
--------------------------------------
Another slight concern re: naming. There's several new things based on a
"Settings" object. (class names, method names, etc.). The definition of this
class is it holds "properties used for external parameter overrides".
There's a tradeoff to be made - between simple names (like "settings") and
being overly general (when thinking long term since these are part of the
official external APIs of UIMA.
So I'm wondering if Setting is too general for it's meaning, and whether or not
it should have a name closer to its definition?
> Provide method to access individual external override settings
> --------------------------------------------------------------
>
> Key: UIMA-5043
> URL: https://issues.apache.org/jira/browse/UIMA-5043
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Reporter: Burn Lewis
> Assignee: Burn Lewis
> Priority: Minor
> Fix For: 2.9.0SDK
>
>
> The framework loads the external override settings and uses them in any
> configuration parameter that has an external override name attached, Users
> have asked for the ability to access these values directly without the
> indirection of configuration parameter entries in descriptors. Currently the
> complete Settings object that holds all the external override settings loaded
> by the framework is accessible via UimaContextAdmin.
> An improvement would be to allow individual values to be read using a method
> in the UimaContext interface, perhaps:
> String getExternalOverride(String name)
> String[] getExternalOverrideArray{String name)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
