Richard Eckart de Castilho created UIMA-6392:
------------------------------------------------
Summary: Better delegate key generation
Key: UIMA-6392
URL: https://issues.apache.org/jira/browse/UIMA-6392
Project: UIMA
Issue Type: New Feature
Components: uimaFIT
Reporter: Richard Eckart de Castilho
Assignee: Richard Eckart de Castilho
Fix For: 3.3.0uimaFIT
When building an aggregate using the uimaFIT {{AggregateBuilder}} or even the
{{createEngine(AED, AED, ...)}} method, uimaFIT auto-generates the delegate
keys. For example, if there is a name set in the metadata, then this is used
and the index of the delegate is appended to it. But there are problems with
the current approach.
First problem is that for delegate aggregates, we simply get {{null-0}} if
these aggregates do not have a name in their metadata. That could be improved
at least to something like {{aggregate-0}}.
Second problem is that the name set in the metadata is not sanitized in any way
before being used as a delegate key. This means the name could contain e.g.
slashes {{/}} which would then go into the qualified context name of the
delegate and at that point it would mess up the context namespace hierarchy,
placing delegates apparently at deeper levels than they actually are. So some
sanitation would be called for here.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
