[
https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432990#comment-15432990
]
Richard Eckart de Castilho commented on UIMA-5043:
--------------------------------------------------
As said before: I don't see any benefit in UIMAJ Core endorsing a global
context. It can enable it, but managing a global context should be the task of
an application (that is living exclusively in its context). That's why
overrides should be bound to a UimaContext and the UimaContext should be
scoped... and not just hang around globally. I see how declaring one context to
be the global one can be useful in UIMA-AS or DUCC where a process/JVM is
basically exclusively used to run a single UIMA pipeline/component... but
that's UIMA-AS/DUCC and not UIMAJ-Core.
> 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)
