You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-dev@axis.apache.org by "Christian Gross (JIRA)" <ax...@ws.apache.org> on 2005/07/12 13:36:09 UTC
[jira] Created: (AXIS-2111) Naming Conventions and Code Generation
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
[jira] Resolved: (AXIS-2111) Naming Conventions and Code Generation
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ 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
[jira] Commented: (AXIS-2111) Naming Conventions and Code Generation
Posted by "Davanum Srinivas (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2111?page=comments#action_12315555 ]
Davanum Srinivas commented on AXIS-2111:
----------------------------------------
Christian,
plz give me something to work with. the changes from nov to 1.2.1 was unavoidable. believe me, i tried. we will try hard not to change anymore. it should give you some respite to hear that axis has passed the standalone tck for saaj and jaxrpc AND j2ee tck for jonas and geronimo. So believe me we won't be making anymore changes than that are absolutely needed. as there are too many folks dependent on it.
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
[jira] Commented: (AXIS-2111) Naming Conventions and Code Generation
Posted by "Christian Gross (JIRA)" <ax...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/AXIS-2111?page=comments#action_12315572 ]
Christian Gross commented on AXIS-2111:
---------------------------------------
I am having problems with the Amazon, Google Word Sense, and Paypal WSDL's. Most of the samples and distributed libraries are coded depending on a certain release of the Axis API's.
Part of the problem relates back to the jar files. As much as we would like to say it is not an issue, it is. When you use Version X of Axis, you version Y of the WSDL, and version Z of the XML jars, etc. I find things becoming too brittle for my liking. Even if the generated code generates a neutral interface, the implementation seems to be creaping along.
I do realize that I am whining without any solutions, but this creep does not seem to be as big of an issue with .NET as I generate both .NET and Java code.
> 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