[
https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15416017#comment-15416017
]
Richard Eckart de Castilho commented on UIMA-5043:
--------------------------------------------------
We recently had a conversation about adding APIs that are then set in stone. So
adding API more conservatively (i.e. adding a single method) might be
preferable to adding multiple methods.
It might even be a good idea to decouple the new method from existing API, e.g.
by introducing a UimaContextHolder with getContext() and setContext() method
that encapsulates this particular concern only (this is what Spring does e.g.
with the SecurityContextHolder).
Settings is an interface - not the place to be adding such a concern.
What kind of end-user are you imagining?
> 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)
