svn commit: r1820902 - in /uima/uv3/uimaj-v3/trunk/uimaj-core/src/main/resources/org/apache/uima: UIMAException_Messages.properties semibuiltins.xml

[sc...@apache.org]

Author: schor
Date: Thu Jan 11 17:41:24 2018
New Revision: 1820902

URL: http://svn.apache.org/viewvc?rev=1820902&view=rev
Log:
[UIMA-5664][UIMA-5698] add new semibuiltin def, and some error msgs

Modified:
    uima/uv3/uimaj-v3/trunk/uimaj-core/src/main/resources/org/apache/uima/UIMAException_Messages.properties
    uima/uv3/uimaj-v3/trunk/uimaj-core/src/main/resources/org/apache/uima/semibuiltins.xml

Modified: uima/uv3/uimaj-v3/trunk/uimaj-core/src/main/resources/org/apache/uima/UIMAException_Messages.properties
URL: http://svn.apache.org/viewvc/uima/uv3/uimaj-v3/trunk/uimaj-core/src/main/resources/org/apache/uima/UIMAException_Messages.properties?rev=1820902&r1=1820901&r2=1820902&view=diff
==============================================================================
--- uima/uv3/uimaj-v3/trunk/uimaj-core/src/main/resources/org/apache/uima/UIMAException_Messages.properties (original)
+++ uima/uv3/uimaj-v3/trunk/uimaj-core/src/main/resources/org/apache/uima/UIMAException_Messages.properties Thu Jan 11 17:41:24 2018
@@ -567,6 +567,8 @@ JCAS_OLDSTYLE_REF_TO_NONJCAS_TYPE = JCas
 JCAS_MAKING_ABSTRACT_INSTANCE = A CAS iterator or createFS call is trying to make an instance of type "{0}", but that type has been declared "abstract" in JCas, and no instances are allowed to be made.
 JCAS_UNSUPPORTED_OP_NOT_TCAS = The method "{0}" is not supported by this JCAS because it is not associated with a TCAS view of a CAS, but rather just with a base CAS.
 JCAS_CLASS_INITIALIZED_BEFORE_TYPE_SYSTEM_COMMIT = A JCas class is being loaded and initialized (by non-framework user code) before the type system with the corresponding type has been set up and committed.\nThis is not allowed in UIMA v3 because the static class initialization code needs access to the type system in order to bridge the JCas class definition to the corresponding type system type.\nYou can fix this by reordering your code to do the commit for the type system first,\nor if you're using a form like Class.forName("myJCasClass"), you can use the alternative API which only loads (but doesn''t run the initialization: Class.forName("myJCasClass", false, this.getClass().getClassLoader()).
+JCAS_MISSING_GETTER = JCas class {0} with feature {1} but is missing a 0 argument getter.  This feature will not be used to maybe expand the type's feature set.
+JCAS_MISSING_TYPEINDEX = The Class "{0}" matches a UIMA Type, and is a subtype of uima.cas.TOP, but is missing the JCas typeIndexId.
 SOFANAME_ALREADY_EXISTS = A sofaFS with name {0} has already been created.
 SOFADATA_ALREADY_SET = Data for Sofa feature {0} has already been set.
 SOFANAME_NOT_FOUND = No sofaFS with name {0} found.

Modified: uima/uv3/uimaj-v3/trunk/uimaj-core/src/main/resources/org/apache/uima/semibuiltins.xml
URL: http://svn.apache.org/viewvc/uima/uv3/uimaj-v3/trunk/uimaj-core/src/main/resources/org/apache/uima/semibuiltins.xml?rev=1820902&r1=1820901&r2=1820902&view=diff
==============================================================================
--- uima/uv3/uimaj-v3/trunk/uimaj-core/src/main/resources/org/apache/uima/semibuiltins.xml (original)
+++ uima/uv3/uimaj-v3/trunk/uimaj-core/src/main/resources/org/apache/uima/semibuiltins.xml Thu Jan 11 17:41:24 2018
@@ -80,5 +80,22 @@
         </featureDescription>
       </features>
     </typeDescription>
+  <typeDescription>
+      <name>org.apache.uima.jcas.cas.Int2FS</name>
+      <description>map from ints to Feature Structures</description>
+      <supertypeName>uima.cas.TOP</supertypeName>
+      <features>
+        <featureDescription>
+          <name>fsArray</name>
+          <description>internal use</description>
+          <rangeTypeName>uima.cas.FSArray</rangeTypeName>
+        </featureDescription>
+        <featureDescription>
+          <name>intArray</name>
+          <description>internal use</description>
+          <rangeTypeName>uima.cas.IntegerArray</rangeTypeName>
+        </featureDescription>
+      </features>
+    </typeDescription>
   </types>
 </typeSystemDescription>