[UIMA-5704] uv3 edge case failures in setting up JCas

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 3.0.0SDK
• Component/s: Core Java Framework
• Assignee: Marshall Schor
• Reporter: Marshall Schor
• Created: 16/Jan/18 16:31
• Updated: 16/Jan/18 16:59
• Resolved: 16/Jan/18 16:59

Description

After adding the capability to merge from JCas class definitions into existing type systems, some edge cases appeared causing failures or replication in conformance testing and setting up the offsets in JCas classes when loading them with type systems.  

Rework to remove redundant checking, and insure offsets are set up in all cases.

Use a simplified supertype/superclass validity checker.

Remove 2nd map used just for class loader associated with pears (not needed).

make type2jcci map only have entries for types having loaded JCas classes (others return null).

Insure updateOrValidateAllCallSitesForJCasClass is called for each combo of a type system and class loader, to either set it up, or validate the offsets.

fix a bug setting the threadlocal used for a previous (alpha) version of some jcas class impl - in case those jcas classes are hanging around (one is, in a PEAR test case)

Skip conformance checking for built-ins.