You are correct, in the edge case we saw earlier that triggered this line of thinking.
If a user constructs a pipeline without PEARs, all the user code called by the framework is normally also loaded by the UIMA framework via that extension class loader. So normally, components using a resource manager with a custom extension classloader won't encounter this. But I'll take a crack at adding this to the docs... :-) -Marshall On 8/19/2016 5:59 PM, Richard Eckart de Castilho wrote: > On 19.08.2016, at 23:50, sc...@apache.org wrote: >> + <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 of this, you cannot have multiple pipelines accessing a CAS in >> read-only mode if one or more of those >> + pipelines contains a PEAR. > This applies to any components using a resource manager with a custom > extension classloader, right? > PEARs are only one specific case in which an extension classloader is being > used. > > Cheers, > > -- Richard
