-
Deprecated InterfacesInterfaceDescriptionAs of release 2.3.0, use UimaContext insteadAs of release 2.3.0, use CasAnnotator_ImplBase or JCasAnnotator_ImplBase insteadAs of release 2.3.0, use JCasAnnotator_ImplBase insteadAs of release 2.3.0, use CasAnnotator_ImplBase or JCasAnnotator_ImplBase insteadAs of v2.0,
AnalysisEngineDescriptionshould be used instead. This interface no longer defines any additional methods beyond those in AnalysisEngineDescription.As of v2.0,AnalysisEngineshould be used instead. This interface no longer defines any additional methods beyond those in AnalysisEngine.useFeaturePathuse AnnotationBase insteaduse Annotation insteaduse BooleanArray insteaduse ByteArray insteaduse DoubleArray insteaduse TOP insteaduse FloatArray insteadunused in v3, only present to avoid compile errors in unused v2 classesuse IntegerArray insteaduse LongArray insteaduse ShortArray insteaduse Sofa insteaduse StringArray insteadAs of v2.0, this is no longer needed. CAS views can now be obtained directly using String identifiers, through the methodCAS.getView(String).As of v2.0, CAS Initializers are deprecated. A component that performs an operation like HTML detagging should instead be implemented as a "multi-Sofa" annotator. See org.apache.uima.examples.XmlDetagger for an example.As of v2.0, CAS Initializers are deprecated. A component that performs an operation like HTML detagging should instead be implemented as a "multi-Sofa" annotator. See org.apache.uima.examples.XmlDetagger for an example.As of v2.0, CAS Initializers are deprecated. A component that performs an operation like HTML detagging should instead be implemented as a "multi-Sofa" annotator. See org.apache.uima.examples.XmlDetagger for an example.As of v2.0 CAS Initializers are deprecated.use FSArray instead
-
Deprecated ClassesClassDescriptionAs of release 2.3.0, use CasAnnotator_ImplBase or JCasAnnotator_ImplBase insteadAs of release 2.3.0, use CasAnnotator_ImplBase or JCasAnnotator_ImplBase insteadAs of release 2.3.0, use JCasAnnotator_ImplBase insteadsince v2.0since v2.0As of v2.0, CAS Initializers are deprecated. A component that performs an operation like HTML detagging should instead be implemented as a "multi-Sofa" annotator. See org.apache.uima.examples.XmlDetagger for an example.As of v2.0, CAS Initializers are deprecated. A component that performs an operation like HTML detagging should instead be implemented as a "multi-Sofa" annotator. See org.apache.uima.examples.XmlDetagger for an example.As of v2.0, CAS Initializers are deprecated.For backwards compatibility with Capability Language Flow only. User-developed Flow Controllers should not use this.As of v2.0, CAS Initializers are deprecated.As of v2.0, use
CasToInlineXmlinstead.
-
Deprecated ExceptionsExceptionsDescriptionThe Constraint Parser is not supported in externally released versions of UIMA
-
Deprecated FieldsFieldDescriptionAs of v2.0, this is replaced by
CAS.NAME_DEFAULT_SOFA, and the value has changed. In general, user code should not need to refer to this name.SOAP protocol is no longer supported since UIMA v3.3.0. Constant to be removed in UIMAv4.SOAP protocol is no longer supported since UIMA v3.3.0. Constant to be removed in UIMAv4.XInclude is no longer supported
-
Deprecated MethodsMethodDescriptionThis is no longer used by the framework and was never intended for users to call. Use {#link #process(CAS)} instead.As of v2.0, annotators no longer need to explicitly call this method. CAS views can now be obtained directly by the method
CAS.getView(String), and the framework will automatically do the necessary Sofa mappings.As of v2.0, annotators no longer need to explicitly call this method. CAS views can now be obtained directly by the methodCAS.getView(String), and the framework will automatically do the necessary Sofa mappings.never called anymore - getAdditionalAttributes called insteadno longer needed, remove call to thisas of 2.2.2 Now called automatically internally when neededUseFeatureStructure.getIndexed()insteadUseFeatureStructure.setIndexed(int[])insteaduse createCas(int initialHeapSize)Usereset()instead.As of v2.0, useCAS.createView(String)instead.As of v2.0, useCAS.getView(String)followed byCAS.getJCas().As of v2.0, use {#getView(String)}. From the view you can access the Sofa data, or callCAS.getSofa()if you truly need to access the SofaFS object.use getTypeClass (spelling fix)Usereset()instead.use form with StringBuilder (not StringBuffer)because uses StringBuffer, not builder, for version 2 compatibility onlyuse getFeatureByBaseName insteadUsegetFeatures()instead.UsegetDirectSubtypes(Type)instead.As of v2.0 CAS Initializers are deprecated.As of v2.0 CAS Initializers are deprecated.As of v2.0 CAS Initializers are deprecated.As of v2.0 CAS Initializers are deprecated.As of v2.0 CAS Initializers are deprecated.As of v2.0 CAS Initializers are deprecated.Doesn't support the new import syntax. Use getCpeComponentDescriptor().findAbsoluteUrl() instead.Doesn't support the new import syntax. Use setCpeComponentDescriptor() instead.As of v2.0 CAS Initializers are deprecated.As of v2.0 CAS Initializers are deprecated.As of v2.0 CAS Initializers are deprecated.this is automatically done by the framework after a new flow object is createdthis is done automatically by the framework with the Flow object is createdsince v2.0As of v2.0, useJCas.createView(String)instead.renamed emptyXXXArrayrenamed emptyXXXArrayrenamed emptyXXXArrayAs of v2.0, use {#getView(String)}. From the view you can access the Sofa data, or callJCas.getSofa()if you truly need to access the SofaFS object.renamed emptyXXXArrayuse instance.jcasType instead - fasternot required, does nothingUseAnnotation.getBegin()instead.Use setMainComponentId() method instead.use Java 7 for this seeFiles.copy(Path, Path, CopyOption...)use Java 7 for this seeFiles.copy(InputStream, Path, CopyOption...)use Java 7 method for this seeFile.createTempFile(String, String, File)use Java 7 method for this seeFiles.size(Path)use Java 7 method for this seeFiles.readAllLines(Path, Charset)use main file util for this, seeFileUtils.file2String(File)if using the default charset is OKuse main file util for this, seeFileUtils.file2String(File, String)if using the default Charset is OKuse Java 7 for this seeFiles.move(Path, Path, CopyOption...)No longer used. Scheduled for removal in UIMA 4.0.Method is deprecated because it should only be used internally. Scheduled for removal in UIMA 4.0.- use getAdditionalAttributes instead- use getAttributes instead- use getAttributes- use getAttributes() instead, don't override it, use getAdditionalAttributes to specify additional onesUseResourceManagerConfiguration.getImports()instead. There may be many imports; this method only returns the first.UseResourceManagerConfiguration.setImports(Import[])instead.org.apache.uima.resource.metadata.TypePriorities.resolveImports(Collection<String>, ResourceManager) Method is deprecated because it should only be used internally. Scheduled for removal in UIMA 4.0.Method is deprecated because it should only be used internally. Scheduled for removal in UIMA 4.0.These parameters only support string values. Better usePearSpecifier.getPearParameters().These parameters only support string values. Better usePearSpecifier.setPearParameters(org.apache.uima.resource.metadata.NameValuePair...).UseRelativePathResolver.getDataPathElements()instead.UseResourceManager.getDataPathElements()instead.Intended just for internal use.As of v2.0,ResourceSpecifierFactory.createAnalysisEngineDescription()should be used instead.UseUimaContext.getDataPathElements()instead.As of v2.0, annotators no longer need to explicitly call this method. CAS views can now be obtained directly by the methodCAS.getView(String), and the framework will automatically do the necessary Sofa mappings.As of v2.0, annotators no longer need to explicitly call this method. CAS views can now be obtained directly by the methodCAS.getView(String), and the framework will automatically do the necessary Sofa mappings.As of v2.0, CAS Initializers are deprecated. A component that performs an operation like HTML detagging should instead be implemented as a "multi-Sofa" annotator. See org.apache.uima.examples.XmlDetagger for an example.As of v2.0,UIMAFramework.produceAnalysisEngine(ResourceSpecifier)should be used instead.As of v2.0,UIMAFramework.produceAnalysisEngine(ResourceSpecifier,int,int)should be used instead.As of v2.0,UIMAFramework.produceAnalysisEngine(ResourceSpecifier,Map)should be used instead.As of v2.0,UIMAFramework.produceAnalysisEngine(ResourceSpecifier,ResourceManager,Map)should be used instead.use Java 7 for this seeFiles.copy(Path, Path, CopyOption...)use Java 7 methods for this seeFiles.createTempDirectory(Path, String, FileAttribute...)use Java 7 methods for this seeFile.createTempFile(String, String, File)use external configuration possibilityuse external configuration possibilityuse new function with log leveluse new function with log leveluse new function with log leveluse external configuration possibilityuse external configuration possibilityuse external configuration possibilityuse external configuration possibilitysince v2.0since v2.0use new function with log leveluse new function with log leveluse new function with log leveluse external configuration possibilityuse external configuration possibilityWhen a logger is used within UIMA, the resource manager is picked up from theUimaContextHolderand if none is available, then the class loader set on theThread.getContextClassLoader()is used. Thus, setting a resource manager for loading message localizations should not be required. Setting a resource manager anyway can lead to resource being registered in the resource manager to not be garbage collected in a timely manner. Also, the logger is shared globally and in a multi-threaded/multi-classloader scenario, it is likely that different threads overwrite each others logger resource manager making it likely that in any given thread the wrong resource manager is used by the logger.UseXMLInputSource.getURL()instead.As of v2.0,XMLParser.parseAnalysisEngineDescription(XMLInputSource)should be used instead.As of v2.0,XMLParser.parseAnalysisEngineDescription(XMLInputSource,ParsingOptions)should be used instead.
-
Deprecated ConstructorsConstructorDescriptionUse
XmiCasSerializer(TypeSystem)instead. The UimaContext reference is never used by this implementation.UseXmiCasSerializer(TypeSystem, Map)instead. The UimaContext reference is never used by this implementation.As of v2.0, TextAnalysisEngine has been deprecated. UseJCasPool(int, AnalysisEngine)instead.XInclude is no longer supported