[
https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15413984#comment-15413984
]
Marshall Schor commented on UIMA-5043:
--------------------------------------
all this can be done in a general way if the access is done via the UIMA
context. In the use-case where the component is not a UIMA component - it
nevertheless has to have a bit of "UIMA" nature to make use of the UIMA
external override things; and because of this, it should be "easy" to have
whatever makes use of the component, pass a UIMA context (corresponding to a
particular UIMA pipeline) to that component. So it could always have a way to
access the appropriate (non-global) context.
I agree with Richard that totally global context are probably not the way to go.
> 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)
