[jira] [Resolved] (UIMA-2478) Add CAS interface method that allows user to obtain a list of Markers associated with a given CAS

["Marshall Schor (JIRA)" <de...@uima.apache.org>]

     [ https://issues.apache.org/jira/browse/UIMA-2478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marshall Schor resolved UIMA-2478.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 2.4.1SDK
         Assignee: Marshall Schor
    
> 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
>            Assignee: Marshall Schor
>             Fix For: 2.4.1SDK
>
>         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