[ 
https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15417182#comment-15417182
 ] 

Burn Lewis commented on UIMA-5043:
----------------------------------

I've tried putting the functions on UIMAFramework (since the other choices were 
interfaces) and do feel uncomfortable with the number of changes.  I like 
Richard's suggestion of exposing a single method to get the context as I can 
then put the access methods on UimaContext where they can be directly used by 
annotators, leaving the thread-local approach only necessary for POJOs, e.g.

String value = aContext.getSetting(paramName);  // For annotators
String value = UimaContextHolder.getContext().getSetting(paramName);   // For 
POJOs

I'd prefer not to expose the Settings_impl object as I don't want to make it 
easy for users to modify it.

As to the initialization from system properties, the applications that use 
UIMA-AS and DUCC provide a descriptor and a few system properties for 
configuration, e.g. framework_impl, logging-properties, datapath, 
external-overrides.  A case could be made that only the first of these MUST be 
global, but currently only the last can be made AE dependent.  We could add 
some new attribute to an AE descriptor to specify the settings files but that 
might make it too easy to accidentally specify different settings on nested AEs.

> 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)

Reply via email to