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

Richard Eckart de Castilho commented on UIMA-5043:
--------------------------------------------------

How do you use external overrides to configure external resources in a way that 
would not be possible without them?

The UIMA framework makes use of static/global configuration in various places - 
but most of them are so deeply hidden in the framework that IMHO hardly anybody 
ever even thinks about overriding them. For most users, the default 
configuration of the UIMA framework is essentially *the UIMA framework*.

In order to ensure proper encapsulation and scoping, everything that goes 
beyond *the framework* should be bound to contexts. Creating a global context 
and promoting users to store configurations in a global context seems like a 
step back - it goes against encapsulation and scoping. I thought this was a bad 
idea already back in the day when the external overrides via a system property 
were introduced - but at that time, I was not part of the PMC and could not do 
anything against it.

Maybe you can outline what situation forces users to make use of a global 
context and why they cannot place their overrides in a properly scoped context?

> 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