[
https://issues.apache.org/jira/browse/UIMA-6056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16868128#comment-16868128
]
Hai-Son Nguyen commented on UIMA-6056:
--------------------------------------
It looks like the current JCasGen process if we have a feature which is a
FSList of FSArray objects the code to collect imports is using hasArrayRange()
to determine access the getJavaRangeArrayElementType() for classes to import.
This would then make the methods if using generics to use the fully qualified
name for the FSArray class like:
FSList<org.apache.uima.jcas.cas.FSArray<?>> instead of the simpler
FSList<FSArray<?>>
What do you think about adjusting the code to check generics and array (Jg line
1239)
Also, was able to access the test cases and still looking at what specifically
to test as these are mostly compiler warnings.
> JCasGen for producing FSArray is a raw type warning
> ---------------------------------------------------
>
> Key: UIMA-6056
> URL: https://issues.apache.org/jira/browse/UIMA-6056
> Project: UIMA
> Issue Type: Bug
> Components: UIMA
> Affects Versions: 3.0.2SDK
> Reporter: Hai-Son Nguyen
> Priority: Minor
> Attachments: patch-uima-6056v1.txt, typeSystemDescriptorTest.xml
>
>
> With the conversion of FSArray into Generic FSArray<> the JCasGen process
> does not handle the Generic type properly and will cause extensive warnings
> in application code.
> The 4 methods generating warnings are:
> xXXX - Feature name, Generic - generic type
> * *public* FSArray getXXX() { *...* }
> * *public* *void* setXXX(FSArray v) \{ ... }
> * *public* Generic getXXX(*int* i) \{ ... }
> * *public* *void* setXXX(*int* i, Generic v) \{ ... }
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
