[
https://issues.apache.org/jira/browse/UIMA-3322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13782732#comment-13782732
]
Richard Eckart de Castilho commented on UIMA-3322:
--------------------------------------------------
Hm, I guess the known types are all those in the type system of the CAS. The
allowed types are only the ones declared in the script. I mean, via the full
type names, types should probably always be accessible, in particular in the
Ruta.appy() scenario or when ruta is running as an AE. In such a case, aliasing
or prefix-importing can be used for shorthand disambiguation. When running
within the workbench, additionally a "from" stanza can be used to tell the
workbench to initialize the CAS with a specific type system. In a AE/apply
scenario, this stanza would be ignored, assuming that the CAS is set up
externally.
> 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)
