axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From j...@apache.org
Subject [jira] Updated: (AXIS-1314) Custom name for implementation class, WSDL2Java
Date Fri, 07 May 2004 08:21:57 GMT
The following issue has been updated:

    Updater: Måns Tånneryd (mailto:mans@tanneryd.com)
       Date: Fri, 7 May 2004 1:20 AM
    Comment:
Testcase for the implementationClassName feature of wsdl2java.
    Changes:
             Attachment changed to webref-20050507.zip
    ---------------------------------------------------------------------
For a full history of the issue, see:

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

---------------------------------------------------------------------
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: 
             WSDL processing
   Versions:
             1.2 Beta

   Assignee: 
   Reporter: Måns Tånneryd

    Created: Wed, 14 Apr 2004 2:39 PM
    Updated: Fri, 7 May 2004 1:20 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 export 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 hardcoded names for the generated implementation class xxxxxSoapBindingImpl.java which
causes some problems. My suggestion would be to add another field in the tojava emitter holding
a custom implementation class name and use that, if it exists, in JavaBindingWriter, JavaDeployWriter
and JavaImplWriter. I have made the appropriate patches and it seems to work just fine. 


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


Mime
View raw message