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 (Commented) (JIRA)" <de...@uima.apache.org> on 2011/10/04 16:20:34 UTC

[jira] [Commented] (UIMA-2147) Generate static fields for type names and feature names in JCas wrappers

    [ https://issues.apache.org/jira/browse/UIMA-2147?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13120155#comment-13120155 ] 

Marshall Schor commented on UIMA-2147:
--------------------------------------

I'm wondering if we need TYPE_NAME, because in order to use it you need the class name, and it's the same as the class name.  It would help me understand better if you could post some pseudo code showing some use cases.
                
> Generate static fields for type names and feature names in JCas wrappers
> ------------------------------------------------------------------------
>
>                 Key: UIMA-2147
>                 URL: https://issues.apache.org/jira/browse/UIMA-2147
>             Project: UIMA
>          Issue Type: Improvement
>          Components: Core Java Framework
>    Affects Versions: 2.3.1
>            Reporter: Richard Eckart de Castilho
>
> It would be convient if the JCas wrapper generator would create static final String fields for feature names and for the type name, e.g.
> public static final String TYPE_NAME = "my.jcastypes.Type";
> public static final String FEAT_BEGIN = "begin";
> This would allow cleaner programming with JCas wrappers in cases where the names are required. In particular it would allow to detect certain errors at compile-time and facilitate refactoring.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira