[
https://issues.apache.org/jira/browse/UIMA-5662?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16293814#comment-16293814
]
Marshall Schor commented on UIMA-5662:
--------------------------------------
Good ideas! +1 to putting the enabler methods on the LowLevelCas. I think
these belong as static methods on the LowLevelCas, not as methods on instances.
I like your idea of try-with-resources, and I think a couple of characters
(e.g. s = ) extra to accommodate the syntax of that is a pretty small syntactic
cost.
I think the Java 8 lambda thing would work except for the pesky exception
issues.
So, I'll probably do something like
{code}
try (w = LowLevelCas.ll_enableGetFSForRef()) {
... some code, including deserializers ...
}
{code}
The ll_enableGetFSForRef would return an AutoClosable, whose close method would
restore the previous value.
You could use this without the try-with-resources, to just set it true or
false. The no arg case would be the same as a *true* arg.
> uv3 support CAS deserialization subsequent low level access
> -----------------------------------------------------------
>
> Key: UIMA-5662
> URL: https://issues.apache.org/jira/browse/UIMA-5662
> Project: UIMA
> Issue Type: Improvement
> Components: Core Java Framework
> Affects Versions: 3.0.0SDK-beta
> Reporter: Marshall Schor
> Assignee: Marshall Schor
> Priority: Minor
> Fix For: 3.0.0SDK
>
>
> Some users depend 1) constant v2-ids for FSs preserved in deserialization and
> serialization, and 2) low level cas API access to these.
> V3 normally doesn't maintain tables linking ids to FSs, as these (unless weak
> refs are used) prevent GC of unreachable FSs.
> Based on a mode, set by -Duima.deserialize_perserve_ids, and also
> controllable by new config option per deserialize call, alter the
> deserialization for those deserializers which know about v2 ids, to put these
> into the map used for low-level CAS access, using the actual v2 ids, and
> change the v3 next available id for future new FSs to be 1 beyond the end.
> The -Duima.deserialize-preserve_ids global setting is needed to handle the
> use case of some annotators using low-level APIs, when part of a pipeline is
> "remoted".
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
