OK, that's an easy enough change. I'll re-open Jira 2147 and fix this (both for UIMA v2 and v3).
Cheers. -Marshall On 7/7/2017 2:58 PM, Richard Eckart de Castilho wrote: > On 07.07.2017, at 03:02, Marshall Schor <[email protected]> wrote: >> [UIMA-2147] adds static constant fields to JCas classes, like _TypeName. >> >> The use seems to be within Java Annotations. >> >> I've noticed that for a small number of builtin UIMA types, there's an >> ambiguity >> in the name. For example, the UIMA "TOP" type has the official name in xml >> of >> "uima.cas.TOP". But the Java class is "org.apache.uima.jcas.cas.TOP". >> >> For most types, including all user-defined types, the Java class and the >> fully >> qualified name match. >> >> For the cases where they don't match, what should be the value assigned to >> _TypeName? I'm guessing if it is for some kind of Java Annotation use, it >> might >> want to be the actual Java class name. This is what it is set to at the >> moment. >> >> If other people have use cases where this should be changed to the official >> xml >> built-in type name, instead, please speak up on this thread :-) . > I would prefer the constant to reflect the type name by which the type can be > looked up in the CAS. > > Cheers, > > -- Richard
