[
https://issues.apache.org/jira/browse/UIMA-2978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13678518#comment-13678518
]
Marshall Schor commented on UIMA-2978:
--------------------------------------
My guess is that this is as it was designed. UIMA has various categories of
ResourceSpecifiers - one of which is the "ConfigurableDataResrouceSpecifier,
which adds "ResourceMetaData (which includes config param settings). But there
are many other kinds (e.g. FileLanguageResourceSpecifier,
FileResourceSpecifier, etc.) which don't have the ResourceMetaData field. I'm
not sure why this is marked as a "bug" - is it more a request for an
enhancement? What is the use case(s) for this, and how important is it to get
a change here into the next release (I see it is marked "major" priority?)?
> CustomResourceSpecifier has no support for resource meta data
> -------------------------------------------------------------
>
> Key: UIMA-2978
> URL: https://issues.apache.org/jira/browse/UIMA-2978
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Richard Eckart de Castilho
>
> The CustomResourceSpecifier provides a way of defining new custom types of
> Resources (e.g. *not* DataResources) which can be acquired via the
> ResourceManager.
> The CustomResourceSpecifier does not support the usual ResourceMetaData,
> which includes support for the typical UIMA parameter configuration. It
> supports only single-valued String parameters.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
