THIS IS A TEST INSTANCE. ALL YOUR CHANGES WILL BE LOST!!!!
...
- a field for each feature
- a reference to the _Type instance
- only for backwards compatibility for low-level access model
- One instance Multiple instances per type system - one per CAS
- has ref to TypeImpl?
- a reference to the CAS View (to support addToIndexes for the right view)
- a ref to a type-system-wide Bitset for index corruption testing
- Constructors
- new Foo(Cas)
- Methods
- getter / setter for all fields
- The setter methods may include index corruption checking code.
- May be code which tests at runtime on each set, whether or not this
- The setter methods may include index corruption checking code.
- indexed getter/setter for fields defined as arrays
- (via inheritance)
- a collection of get/set methods, one per boolean/byte/short.../double/String/TOP/JavaObject and arrays of these, kinds of values.
- The methods take an extra "offset" value, obtained from the Feature.
- Used for backwards compatibility with non-JCas styles, and for serialization and other "generic" operations
- a collection of get/set methods, one per boolean/byte/short.../double/String/TOP/JavaObject and arrays of these, kinds of values.
- getter / setter for all fields
x.y.z.Foo_Type
An instance is loaded when a new x.y.z.Foo(some-cas) is done, lazily.
has
- a ref to the TypeImpl
- a ref to the CAS (an arbitrary view, sometimes updated in v2), used for low level access patterns
Instances are accessed per CAS via
- a Map (kept per CAS) from the x.y.z.Foo Class to the corresponding x.y.z.Foo_type instance.
- The key is a x.y.z.Foo Class object, so instances loaded under different class loaders may have the same class name. This used to happen for PEARS (but not in v3).
- This happens when different generated x.y.z.Foo (due to different merged type systems) are running in the same JVM.
- This used to happen within one pipeline with PEAR switching, where the PEAR might have a different customization of a JCas class. In v3, that doesn't happen; all versions of a customization must be merged.
- If the Map has no entry,
- Load the _Type class itself, if not loaded (Map in TypeSystemImpl instance, key = name string, value = _Type Class).
- Make instance of it, populate map in CAS.svd.
- The key is a x.y.z.Foo Class object, so instances loaded under different class loaders may have the same class name. This used to happen for PEARS (but not in v3).
Gliffy Diagram | ||||
---|---|---|---|---|
|