[
https://issues.apache.org/jira/browse/UIMA-6057?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16880646#comment-16880646
]
Richard Eckart de Castilho commented on UIMA-6057:
--------------------------------------------------
The way you describe it, the AEs are the authoritative source of the type
system. I usually prefer considering the CAS as being the authoritative source.
But to be honest, using uimaFIT blurs it all a bit because one seldom deals
with the type system directly and rather lets the classpath scanning for types
take care of assembling it - which also means that the TS is essentially always
the same for every CAS and every component.
P.S.: the above is from a pipeline builder's perspective. When working in the
context of an annotation editor it is a bit different... there are lots of
different type systems, but within a particular context (e.g. an annotation
project), it is always the same one.
P.P.S.: my thoughts are probably unrelated Peter's and Matthias' use-case.
> Avoid falsely switching classloader
> -----------------------------------
>
> Key: UIMA-6057
> URL: https://issues.apache.org/jira/browse/UIMA-6057
> Project: UIMA
> Issue Type: Bug
> Components: Core Java Framework
> Reporter: Matthias Koch
> Priority: Major
> Attachments: UIMA-6057.diff, classloadertest.zip
>
>
> In some cases the classloader is switched back, although it hasn't be
> switched before processing.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
