[
https://issues.apache.org/jira/browse/UIMA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13703542#comment-13703542
]
Marshall Schor commented on UIMA-2478:
--------------------------------------
I spoke with the originator, and he says:
1) He knew about getCurrentMark()
2) It was package-private, so would need to be made public for his use
3) He saw the inconsistency in havng the createMarker() be in the CAS
interface, but this method not.
4) He envisioned a dream future where lists of markers would be supported, and
wanted to move toward that.
Given this, (summarizing the discussion above:) and the fact that "Markers"
were initially conceived as internal things, and the need for more thought on
architecting a potential future user-facing set of APIs around user needs in
this area (not internal needs), I'll revert this change and make the CASImpl
method getCurrentMark() public; I'll leave the existing createMark in the CAS
Interface to reduce "change" to that interface, pending some further work on
improving this whole area.
> Add CAS interface method that allows user to obtain a list of Markers
> associated with a given CAS
> -------------------------------------------------------------------------------------------------
>
> Key: UIMA-2478
> URL: https://issues.apache.org/jira/browse/UIMA-2478
> Project: UIMA
> Issue Type: New Feature
> Reporter: Benjamin Segal
> Attachments: UIMA-2478.bps.patch
>
>
> Add a convenience function that removes the need for applications that create
> Markers for many CASes to separately manage them (e.g., map CAS to its
> related Marker), and thereby simplify application code.
> Today's current level of support allows a user to create a Marker for a given
> CAS (through the createMarker() method which is part of the CAS interface).
> This proposed support will allow the user to subsequently query a given CAS
> and obtain a complete list of Markers created against this CAS. This function
> is a natural extension to the given level of support (i.e., if one can create
> Marker for a given CAS, one should be able to query the CAS to find said
> Marker.)
> Having this support significant simplifies application code, offering
> advantages from a memory overhead, performance, and maintainability
> standpoint. For example, the application won't need to build and maintain a
> map of CASes to Markers, given the Marker is hanging off the CAS to begin
> with.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
