[
https://issues.apache.org/jira/browse/UIMA-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13783522#comment-13783522
]
Alexandre Patry commented on UIMA-3322:
---------------------------------------
I am not aware neither of a way to access the type system of the current
analysis engine. As Richard suggested, all types known to the CAS could be
available by their long name and we could use imports as defined in UIMA-3303
to use types by their alias or short name.
For {{Ruta.apply()}}, we could add another import statement that would make all
the types known to the CAS available by their short name, like {{IMPORT *;}},
and prepend it automatically to the script.
> 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 not:
> {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
(v6.1#6144)
