[
https://issues.apache.org/jira/browse/UIMA-6258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17178969#comment-17178969
]
Peter Klügl commented on UIMA-6258:
-----------------------------------
This is caused by a restriction of old actions that refer to annotation using a
type. The action tries to identify the annotation using the type for each rule
match separately and thus does not now that it already processed the first
annotation. This behavior can be extended/fixed, but I rather would rewrite the
rules by using more modern language constructs. Is that an option?
> Action FILL only considers first annotation of given type
> ---------------------------------------------------------
>
> Key: UIMA-6258
> URL: https://issues.apache.org/jira/browse/UIMA-6258
> Project: UIMA
> Issue Type: Bug
> Components: Ruta
> Affects Versions: 2.8.1ruta, 3.0.1ruta
> Reporter: Michael Stenger
> Assignee: Peter Klügl
> Priority: Minor
> Fix For: 2.8.2ruta, 3.0.2ruta
>
>
> Hey!
> I think there is a minor bug in the implementation of action FILL, lines
> 79-86 of FillAction.java: Even when multiple annotations of the given type
> are found within/overlapping the range of the matched annotation, only one is
> modified here.
> Consider the following script:
> {code:java}
> DECLARE SomeType (STRING s);
> (CW W){-> SomeType, SomeType};
> CW{-> FILL(SomeType, "s" = "test")}
> {code}
> on the the input text:
> {code:java}
> This is a test.
> {code}
> Here, FILL will only assign the string value to one of the newly created
> SomeType annotations.
> Some clarification would be great. Thanks, Michael.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
