You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@uima.apache.org by "Marshall Schor (JIRA)" <de...@uima.apache.org> on 2017/11/09 15:17:00 UTC

[jira] [Closed] (UIMA-4666) UV3 JCasGen

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

Marshall Schor closed UIMA-4666.
--------------------------------
       Resolution: Fixed
    Fix Version/s: 3.0.0SDK

> UV3 JCasGen
> -----------
>
>                 Key: UIMA-4666
>                 URL: https://issues.apache.org/jira/browse/UIMA-4666
>             Project: UIMA
>          Issue Type: Story
>          Components: Core Java Framework
>            Reporter: Marshall Schor
>             Fix For: 3.0.0SDK
>
>
> Changes to JCasGen approach.
> Allow users an easy migration from existing JCasGen classes
>   - a reporting tool that identifies existing JCas gen classes being used
>   - tooling support for setting up "merged" JCasGen class definitions from multiple sources
>     -- Goal: support PEARs having different (but mergable) JCasGen definitions
> Internal: only one class per type - the xxx_type class is removed in UV3
>   - document migration path for users previously using xxx_type capabilities for low-level CAS operation
> Document use-cases for JCasGen customization and changes possible due to new support for JavaObjects as data in Features.
> Document the use-cases supported, including
>   - A single set of JCasGen classes used for different type systems
>   - External semi-manual merging of JCasGen classes from PEARs and their
>     containers
>   - Continuing to have JCasGen optional



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)