uima-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Peter Klügl (JIRA) <...@uima.apache.org>
Subject [jira] [Commented] (UIMA-3322) Only types from the declared typesystems should be available in RUTA scripts
Date Tue, 01 Oct 2013 07:44:54 GMT

    [ https://issues.apache.org/jira/browse/UIMA-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782689#comment-13782689

Peter Klügl commented on UIMA-3322:

We should do something about it, but we probably should not completely forbid to use types
that are not declared within the script. I am thinking for example of Ruta.apply(CAS, String)
or similar shortcuts. It is something really useful not to take care of the imports in the

However, I have no solution yet. Maybe make the "known type check" optional in ruta-core?

> Only types from the declared typesystems should be available in RUTA scripts
> ----------------------------------------------------------------------------
>                 Key: UIMA-3322
>                 URL: https://issues.apache.org/jira/browse/UIMA-3322
>             Project: UIMA
>          Issue Type: Bug
>          Components: ruta
>    Affects Versions: 2.1.0ruta
>            Reporter: Alexandre Patry
>            Assignee: Alexandre Patry
> RUTA makes all types that are known to the CAS available by their short name. This means
that a type may be available when the script runs in one aggregate but not when it runs in
the other.
> For example, the following script will sometimes work and sometimes not work depending
if the aggregate in which it is executed knows about a type with short name {{MyType}} or
> {noformat}
> PACKAGE com.example.ruta;
> W{->MARK(MyType)};
> {noformat}
> I would expect only types from the typesystems declared in the RUTA script to be allowed.

This message was sent by Atlassian JIRA

View raw message