[
https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15415904#comment-15415904
]
Burn Lewis commented on UIMA-5043:
----------------------------------
Nice. We could make the framework set the thread-local UimaContext whenever
calling annotator methods, and add static methods to some class to call the
appropriate UimaContext methods, e.g.
String getSetting(String name)
String[] getSettingArray{String name)
Set<String> settingNames()
So which class? We could use UimaFramework or UimaContext (in org.apache.uima)
or Settings (in org.apache.uima.util)
Settings may be best since that's what we're dealing with.
Now do we need methods on UimaContext? For an annotator with access to the
UimaContext the path to the Settings object would be a bit shorter than via the
thread-local variable, but not much. For now I'd recommend just the one static
method approach to these variables.
> 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)
