[
https://issues.apache.org/jira/browse/UIMA-5043?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15432867#comment-15432867
]
Marshall Schor commented on UIMA-5043:
--------------------------------------
Since the UimaContextHolder has two classes of methods, one for use by Users,
the other for UIMA framework internal use only, perhaps this should be
reflected in the API / class / interface design? This could be done by
following the UIMA style of having a user-facing Interface API with just those
methods intended to be stable and for users, and having an implementation class
(e.g. UimaContextHolder_impl) in a package with a name part of .. internal ..
or .. impl .. (so that the semantic versioning code knows to exclude it) having
the internal-use only methods as well as the implementation of the user-facing
ones?
> 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)
