Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Message-ID: <1816469931.1083918116638.JavaMail.apache@nagoya>
Date: Fri, 7 May 2004 01:21:56 -0700 (PDT)
From: jira@apache.org
To: axis-dev@ws.apache.org
Subject: [jira] Updated: (AXIS-1314) Custom name for implementation class,
 WSDL2Java
In-Reply-To: <1162491412.1081978784606.JavaMail.apache@nagoya>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

The following issue has been updated:

    Updater: M=E5ns T=E5nneryd (mailto:mans@tanneryd.com)
       Date: Fri, 7 May 2004 1:19 AM
    Comment:
This diff contains the added feature mentioned in this issue as well as upd=
ated documentation. A new testcase for this feature is included in the webr=
ef attachment.
    Changes:
             Attachment changed to diff-20050507.zip
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://issues.apache.org/jira/browse/AXIS-1314?page=3Dhistory

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1314

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: AXIS-1314
    Summary: Custom name for implementation class, WSDL2Java
       Type: Wish

     Status: Unassigned
   Priority: Minor

    Project: Axis
 Components:=20
             WSDL processing
   Versions:
             1.2 Beta

   Assignee:=20
   Reporter: M=E5ns T=E5nneryd

    Created: Wed, 14 Apr 2004 2:39 PM
    Updated: Fri, 7 May 2004 1:19 AM

Description:
I'm working on an eclipse plugin for Axis, http://sourceforge.net/projects/=
soapclipse. One of the things I'd really like to do with the plugin is to e=
xport an existing java class as a web service. This is, in its simplest not=
 very difficult, simply run Java2WSDL followed by WSDL2Java, or rather the =
corresponding emitters. The current Axis implementation has more or less ha=
rdcoded names for the generated implementation class xxxxxSoapBindingImpl.j=
ava which causes some problems. My suggestion would be to add another field=
 in the tojava emitter holding a custom implementation class name and use t=
hat, if it exists, in JavaBindingWriter, JavaDeployWriter and JavaImplWrite=
r. I have made the appropriate patches and it seems to work just fine.=20


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira