cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Beryozkin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CXF-6676) Incorrect Interface Method Name Generation
Date Thu, 19 Nov 2015 21:35:11 GMT

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

Sergey Beryozkin commented on CXF-6676:
---------------------------------------

Please see the test commits in the Development tag. It works as expected. Perhaps this issue
does persist in CXF 2.7.x, but CXF 2.7.18 was the last CXF 2.7.x, please migrate to 3.0.x
or 3.1.x

> Incorrect Interface Method Name Generation
> ------------------------------------------
>
>                 Key: CXF-6676
>                 URL: https://issues.apache.org/jira/browse/CXF-6676
>             Project: CXF
>          Issue Type: Bug
>          Components: JAX-RS
>    Affects Versions: 2.7.18
>            Reporter:  Bharat Savanur
>            Assignee: Sergey Beryozkin
>             Fix For: 3.1.5, 3.0.8, 3.2.0
>
>
> The issue is with interface name that gets generated if there is a special character
in the Resource Path. For ex: 
> Service Impln defn: 
> @Post
> @Path("get-add")
> public Result add(Int a){
> }
> When we generate client interface using WADL (which is generated from the above service
definition) , then interface name has the following structure:
> @Path("get-add")
> public Result postGet-add(Int a);
> We are using WADLTOJAVA for client interface generation.
> The above method name  violates JAVA METHOD NAMING conventions.
>  which results in compilation errors.
> Can you please let me know if there is a solution currently available for this.
> Thanks and Regards,
> Bharat Savanur



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message