axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Closed: (AXIS-1314) Custom name for implementation class, WSDL2Java
Date Mon, 10 May 2004 17:27:56 GMT

   The following issue has been closed.

   Resolver: Davanum Srinivas
       Date: Mon, 10 May 2004 10:27 AM

Applied your patch(es). Please cross-check. Sorry for the delay.

-- dims
View the issue:

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

     Status: Closed
   Priority: Minor
 Resolution: FIXED

    Project: Axis
             WSDL processing
             1.2 Beta

   Reporter: Måns Tånneryd

    Created: Wed, 14 Apr 2004 2:39 PM
    Updated: Mon, 10 May 2004 10:27 AM

I'm working on an eclipse plugin for Axis, 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 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. 

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message