Uses of Class
org.apache.uima.internal.util.Obj2IntIdentityHashMap
Packages that use Obj2IntIdentityHashMap
Package
Description
Implementation and Low-Level API for the CAS Interfaces.
-
Uses of Obj2IntIdentityHashMap in org.apache.uima.cas.impl
Fields in org.apache.uima.cas.impl declared as Obj2IntIdentityHashMapModifier and TypeFieldDescription(package private) final Obj2IntIdentityHashMap
<TOP> CommonSerDesSequential.fs2addr
a map from a fs to its addr in the modeled heap, == v2 style addr created during serialization and deserialization used during serialization to create addr info for index info serialization For delta, the addr is the modeled addr for the full CAS including both above and below the line.private final Obj2IntIdentityHashMap
<TOP> BinaryCasSerDes4.Serializer.fs2seq
convert between FSs and "sequential" numbers This is for compression efficiency and also is needed for backwards compatibility with v2 serialization forms, where index information was written using "sequential" numbers Note: This may be identity map, but may not in the case for V3 where some FSs are GC'd Contrast with fs2addr and addr2fs in csds - these use the pseudo v2 addresses as the intprivate Obj2IntIdentityHashMap
<TOP> XmiSerializationSharedData.fsToXmiId
V3: FSs have an id - use that.private final Obj2IntIdentityHashMap
<CommonList> CasCompare.node_indexes
a map from list nodes which might be removed, to their place in the fss array list The index is 1 more, to avoid colliding with the 0 value, used for missing valueMethods in org.apache.uima.cas.impl with parameters of type Obj2IntIdentityHashMapModifier and TypeMethodDescription(package private) void
BinaryCasSerDes.addIdsToIntVector
(Collection<TOP> fss, IntVector v, Obj2IntIdentityHashMap<TOP> fs2addr) (package private) void
BinaryCasSerDes.addIdsToIntVector
(Set<TOP> fss, IntVector v, Obj2IntIdentityHashMap<TOP> fs2addr) private static int
CASSerializer.convertArrayIndexToAuxHeapAddr
(BinaryCasSerDes bcsd, int index, TOP fs, Obj2IntIdentityHashMap<TOP> fs2auxOffset) The offset in the modeled heaps:private static int
CASSerializer.convertArrayIndexToMainHeapAddr
(int index, TOP fs, Obj2IntIdentityHashMap<TOP> fs2addr) private void
BinaryCasSerDes.extractFsToV2Heaps
(TOP fs, boolean isMarkSet, Obj2IntIdentityHashMap<TOP> fs2addr) called in fs._id order to populate heaps from all FSs.(package private) int[]
BinaryCasSerDes.getDeltaIndexedFSs
(MarkerImpl mark, Obj2IntIdentityHashMap<TOP> fs2addr) (package private) int[]
BinaryCasSerDes.getIndexedFSs
(Obj2IntIdentityHashMap<TOP> fs2addr) Serialization support *(package private) static void
CASSerializer.scanModifications
(BinaryCasSerDes bcsd, CommonSerDesSequential csds, CASImpl.FsChange[] fssModified, Obj2IntIdentityHashMap<TOP> fs2auxOffset, List<CASSerializer.AddrPlusValue> chgMainAvs, List<CASSerializer.AddrPlusValue> chgByteAvs, List<CASSerializer.AddrPlusValue> chgShortAvs, List<CASSerializer.AddrPlusValue> chgLongAvs) Scan the v3 fsChange info and produce v2 style info into chgXxxAddr, chgXxxValue A prescan approach is needed in order to write the number of modifications preceding the write of the values (which unfortunately were written to the same stream in V2).