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

Alexandre Patry commented on UIMA-3322:
---------------------------------------

{quote}
I am in favor of a boolean parameter in the analysis engine (e.g., set in 
Ruta.apply()), which states that the developer took care of the problem: You 
will be able to use all types of the CAS without correct imports. Just an idea 
and not yet well-conceived.
{quote}

You are right, it is a better idea.

{quote}
We create a "model" of the known types of a script file, which will help us to 
identify/solve the problems with the short names (e.g., in AAEs). Mind that we 
will probably need a model for each script file, which can be done in 
RutaEnvironment. In order to aquire this model, there seems to be no other way 
than store this information while parsing the script files. As a consequence we 
will need to load, for example, the imported type system descriptors. Thus, 
UIMA-3303 should be done before we tackle this issue. 
{quote}

That is a great summary. I already started work last week to import only the 
types from the typesystems declared in the script. I could add a 
{{strictImport}} boolean parameter to enable or disable this feature and that 
would close this issue. I could then go on with UIMA-3303 and finish UIMA-3292.


> 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)

Reply via email to