You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@uima.apache.org by "Joern Kottmann (JIRA)" <de...@uima.apache.org> on 2011/08/31 13:56:09 UTC

[jira] [Closed] (UIMA-2222) CasDocumentProvider should be suitable for any kind of ICasEditor

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

Joern Kottmann closed UIMA-2222.
--------------------------------

    Resolution: Fixed

> CasDocumentProvider should be suitable for any kind of ICasEditor
> -----------------------------------------------------------------
>
>                 Key: UIMA-2222
>                 URL: https://issues.apache.org/jira/browse/UIMA-2222
>             Project: UIMA
>          Issue Type: Improvement
>          Components: CasEditor
>            Reporter: Joern Kottmann
>            Assignee: Joern Kottmann
>             Fix For: 2.3.2SDK
>
>
> The Cas Editor is build around the idea that a Document Provider is responsible to manage CASes for various ICasEditor implementations. The CAS handling itself should be independent of their content, therefore a CAS which contains a text view can be managed (created, serialized, delted) in the same way as a CAS which contains an audio view.
> Currently the CasDocumentProvider extends the eclipse text Document Provider, this inheritance should be removed, and the CasDocumentProvider should be independent of the text Document Provider.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira