Author: schor
Date: Sun Aug 21 17:58:17 2016
New Revision: 1757073
URL: http://svn.apache.org/viewvc?rev=1757073&view=rev
Log:
no Jira - update details of operational data being updated for read-only CASes
in other edge cases
Modified:
uima/uimaj/trunk/uima-docbook-references/src/docbook/ref.cas.xml
Modified: uima/uimaj/trunk/uima-docbook-references/src/docbook/ref.cas.xml
URL:
http://svn.apache.org/viewvc/uima/uimaj/trunk/uima-docbook-references/src/docbook/ref.cas.xml?rev=1757073&r1=1757072&r2=1757073&view=diff
==============================================================================
--- uima/uimaj/trunk/uima-docbook-references/src/docbook/ref.cas.xml (original)
+++ uima/uimaj/trunk/uima-docbook-references/src/docbook/ref.cas.xml Sun Aug 21
17:58:17 2016
@@ -1123,9 +1123,14 @@ FSIterator it = cas.createFilteredIterat
arise because some UIMA Framework activities may update internal CAS data
structures.</para>
<para>Operational data is updated while running a pipeline when a PEAR is
entered or exited,
- because PEARs establish new class loaders and can potentially switch the
JCas classes being used.
+ because PEARs establish new class loaders and can potentially switch the
JCas classes being used
+ (This happens because the class loaders might define different JCas cover
classes
+ implementing the same UIMA type).
Because of this, you cannot have multiple pipelines accessing a CAS in
read-only mode if one or more of those
- pipelines contains a PEAR.
+ pipelines contains a PEAR. There are other edge cases where this may
happen as well; for example, if you are
+ running a pipeline with an Extension Class Loader,
+ and have a callback routine loaded under a different class loader, UIMA
will switch the JCas classes when
+ calling the callback.
</para>
</section>
</chapter>
\ No newline at end of file
