Return-Path: 
 <issues-return-36289-apmail-cxf-issues-archive=cxf.apache.org@cxf.apache.org>
X-Original-To: apmail-cxf-issues-archive@www.apache.org
Delivered-To: apmail-cxf-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id D032E184C6
	for <apmail-cxf-issues-archive@www.apache.org>;
 Thu, 19 Nov 2015 10:27:11 +0000 (UTC)
Received: (qmail 73004 invoked by uid 500); 19 Nov 2015 10:27:11 -0000
Delivered-To: apmail-cxf-issues-archive@cxf.apache.org
Received: (qmail 72978 invoked by uid 500); 19 Nov 2015 10:27:11 -0000
Mailing-List: contact issues-help@cxf.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@cxf.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@cxf.apache.org>
List-Post: <mailto:issues@cxf.apache.org>
List-Id: <issues.cxf.apache.org>
Reply-To: dev@cxf.apache.org
Delivered-To: mailing list issues@cxf.apache.org
Received: (qmail 72918 invoked by uid 99); 19 Nov 2015 10:27:11 -0000
Received: from arcas.apache.org (HELO arcas) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 19 Nov 2015 10:27:11 +0000
Received: from arcas.apache.org (localhost [127.0.0.1])
	by arcas (Postfix) with ESMTP id EE7892C1F5E
	for <issues@cxf.apache.org>; Thu, 19 Nov 2015 10:27:10 +0000 (UTC)
Date: Thu, 19 Nov 2015 10:27:10 +0000 (UTC)
From: " Bharat Savanur (JIRA)" <jira@apache.org>
To: issues@cxf.apache.org
Message-ID: <JIRA.12913155.1447600376000.121071.1447928830974@Atlassian.JIRA>
In-Reply-To: <JIRA.12913155.1447600376000@Atlassian.JIRA>
References: <JIRA.12913155.1447600376000@Atlassian.JIRA>
 <JIRA.12913155.1447600376223@arcas>
Subject: [jira] [Comment Edited] (CXF-6676) Incorrect Interface Method Name
 Generation
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


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

 Bharat Savanur edited comment on CXF-6676 at 11/19/15 10:27 AM:
-----------------------------------------------------------------

Sorry for late reply was travelling. Yes i still see the errror. Can you please  let me know the process that you followed.

The process that i followed is:

a) Create a CXF JAXRSService implemention like:
  public class AddServiceImpl{

   @Path ("get-add-method")
   public Integer getAddMethods(){
     
    }
}

b) Now CXF will generate automatic wadl from the service definition above which would be something like below:

<resource path="/">
      <resource path="/get-add-method">
        <param name="id" style="template"/>
        <method name="GET">
          <response>
           <representation mediaType="application/xml" element="ns:thebook"/>
          </response>
        </method>
      </resource>
   </resource>

c) Now i use above wadl with command line argument : WADLToJava to generate interfaces namely Resource.java.

d)  The interface does gets generated but the method name is erroneous. Its like given below:

public interface Resource {

@Path("get-add-methods")
Int getGet-add-methods();
}

The above definition of method name is incorrect which is causing issue. This we are passing to the JAXRSProxyClient to generate proxies for calling the service exposed.

Can you please let me if there is a way to do that.


was (Author: bsavanur):
Sorry for late reply was travelling. Yes i still see the errror. Can you please  let me know the process that you followed.

The process that i followed is:

a) Create a CXF JAXRSService implemention like:
  public class AddServiceImpl{

   @Path ("get-add-method")
   public void getAddMethods(){
     
    }
}

b) Now CXF will generate automatic wadl from the service definition above which would be something like below:

<resource path="/">
      <resource path="/get-add-method">
        <param name="id" style="template"/>
        <method name="GET">
          <response>
           <representation mediaType="application/xml" element="ns:thebook"/>
          </response>
        </method>
      </resource>
   </resource>

c) Now i use above wadl with command line argument : WADLToJava to generate interfaces namely Resource.java.

d)  The interface does gets generated but the method name is erroneous. Its like given below:

public interface Resource {

@Path("get-add-methods")
Int getGet-add-methods();
}

The above definition of method name is incorrect which is causing issue. This we are passing to the JAXRSProxyClient to generate proxies for calling the service exposed.

Can you please let me if there is a way to do that.

> 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)