myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Nicolucci (JIRA)" <>
Subject [jira] [Commented] (MYFACES-4233) Support generics return type on myfaces-builder-plugin
Date Thu, 31 May 2018 16:54:00 GMT


Paul Nicolucci commented on MYFACES-4233:

My initial thought here is that we might need to update our qdox version that is being used.
Currently the 1.12 version is used and in
we're doing the following:

private String getInnerSourceCode(JavaDocBuilder builder, ComponentMeta component)
//Get declaration signature in a way that we don't need
                //to declare imports.
                String declaration = method.getDeclarationSignature(true);

It's possible that's not dealing with Generics properly.

> Support generics return type on myfaces-builder-plugin
> ------------------------------------------------------
>                 Key: MYFACES-4233
>                 URL:
>             Project: MyFaces Core
>          Issue Type: Bug
>          Components: JSR-372
>            Reporter: Eduardo Breijo
>            Priority: Minor
> On the JIRA issue below, there was an issue with the _UIWebsocket.getEventNames() method
where the generic <String> in the return type of the method was missing in the auto-generated
file UIWebsocket.
> {code:java}
> //BEGIN CODE COPIED FROM javax.faces.component._UIWebsocket 
> public java.util.Collection getEventNames()
> {code}
> JIRA issue:
> To workaround this, the api/src/main/resources/META-INF/componentClass20.vm file was
modified to actually generate the getEventNames() method with the correct return type. 
> But I think we should fix this in the myfaces-builder-plugin, and then revert back
the changes in the componentClass20.vm and javax.faces.component._UIWebsocket files.
> I'm not familiar with the myfaces-builder-plugin, so any help here would be appreciated.

This message was sent by Atlassian JIRA

View raw message