axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Created: (AXIS-1379) When WSDL2Java creates a new class for a complex type, it shouldn't overwrite that class if it exists
Date Wed, 02 Jun 2004 21:32:53 GMT

  A new issue has been created in JIRA.

View the issue:

Here is an overview of the issue:
        Key: AXIS-1379
    Summary: When WSDL2Java creates a new class for a complex type, it shouldn't overwrite
that class if it exists
       Type: Improvement

     Status: Unassigned
   Priority: Major

    Project: Axis
             WSDL processing

   Reporter: Rick Herrick

    Created: Wed, 2 Jun 2004 2:32 PM
    Updated: Wed, 2 Jun 2004 2:32 PM
Environment: Axis 1.1 through Ant 1.6.1 on Windows 2000

I have a class for a Web service called Manage.  Some of the service methods on this class
accept or return a class called UserProfile.  I have my own implementation of this class,
but that implementation is overwritten by an auto-generated implementation.  Instead, if WSDL2Java
finds an existing file for a complexType, it should leave that existing file.  This would
be consistent with the current behavior with the generated *SoapBindingImpl: if the *SoapBindingImpl
file exists, it's not overwritten.  Although the generated code for the complex type is useful
(e.g. the generated typeDesc saves a ton of work), there are times when, just like the SOAPBindingImpl,
developers need to add other custom code to the complex type class.  In my case, I have to
add a constructor to initialize the members of the UserProfile class, since the profile that
should be stored in the object is encoded in its persistent store and needs to be interpreted
into the various members of the data class.

It would be even better if there was a flag that could control whether overwrites happened
or not, e.g. forceOverwrite="true" would mean that the complex types and *SoapBindingImpl
classes would be overwritten.

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