[ http://issues.apache.org/jira/browse/AXIS-2111?page=all ]
Davanum Srinivas resolved AXIS-2111:
------------------------------------
Resolution: Incomplete
closing this bug as Christian has opened other actionable bugs.
thanks,
dims
> Naming Conventions and Code Generation
> --------------------------------------
>
> Key: AXIS-2111
> URL: http://issues.apache.org/jira/browse/AXIS-2111
> Project: Apache Axis
> Type: Wish
> Components: WSDL processing
> Reporter: Christian Gross
>
> Up until November of last year Axis was a very good and stable Web Services
> platform. And ever since then problems with the WSDL generation are cropping
> up left right and center. Specially, I am generating stubs for Amazon,
> Google, EBay, and PayPal. The biggest major problem I have is that the names
> are constantly changing. Granted some of these problems are related to the
> companies themselves, but they are doing it because Axis keeps changing.
> Let me give an example. Amazon has a hideous WSDL file. For the past year
> of so Amazon has made little changes so that the code generators generate
> nicer code. However, the code that is generated is specific to a version of
> Axis. Change the Axis version, and the code breaks. What really worries me
> is that some WSDL's and XSD's are dependent on 1.2 RC2.
> I know part of the software development process is to update and fix, and
> that developers should not rely on release candidate editions, however, the
> WSDL generator is giving me headaches. What especially concerns me are the
> changes of the identifiers in minor version numbers.
> Consider it as follows, you have bug fixes, but because a minor version
> changed the identifiers it means changing the source code and updating the
> identifiers. If you have a major application, you will not release a version
> of your application because it will cost too much. This means your
> application would contain the bugs and potentially the security issues.
--
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
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
