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 Sanjiva Weerawarana <sa...@opensource.lk> on 2006/03/29 21:31:56 UTC
Re: [jira] Resolved: (AXIS2-515) WSDL2Java generates uncompilable
code.
On Wed, 2006-03-29 at 11:37 +0100, Ajith Harshana Ranabahu (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/AXIS2-515?page=all ]
>
> Ajith Harshana Ranabahu resolved AXIS2-515:
> -------------------------------------------
>
> Resolution: Fixed
>
> I've generated the code and tested it against the salesforce service. I
> got the successful answers and I'm confident that if we write an
> application to utilize salesforce, the generated stub can be used
> effectively for that.
Excellent! Simon, can you verify this please? It would be idea if you
could check it out now rather than waiting for the next release.
> Here are the answers for the other questions
> a) This is the default behavior. I agree that having a 5 Mb source file
> is hard to handle but I've made sure that it works and the can be
> easily compiled through the generated build file. You can use the -ss
> -sd -g option set to completely expand the generated classes.
+1.
> c). Yes. This seems to be the case and I'll have a look at this. Anyway I
> think this is better marked as a seperate Jira to keep track of it
OK.
> d) Unfortunatley yes.
Is that removable??
> e) The reason is that you have elements and types
> in the same name. Since ADB generates classes for both toplevel
> elements and types, it gives unique names to avoid conflicts.
Can we improve this? In particular, it seems to me we only need to
generate a class for a type if its used in a non-top level element. If
its a top level elem then we generate the class for the elem ..
Maybe its too smart of an optimization but would appreciate your
thoughts.
Sanjiva.