Hi Amila, I used a last weeks nightly build. I tried it again with the one from 3 dec and indeed, a E suffix is appended to the classname. The generated code is for Simon's wsdl.
Can you (or someone else) explain me the differences between the Axis and Axis2 approach in this? Because Axis seems to generate code which makes more sense than Axis2. Therefore I am using Axis now, while I would prefer to use Axis2. Maybe I should skip code generation and provide the classes myself, although this will be time-consuming. Thanks, Sietse ________________________________ From: Amila Suriarachchi [mailto:[EMAIL PROTECTED] Sent: 03 December 2007 13:27 To: [email protected] Subject: Re: Strange generated java class names Are you sure you use the nighly build? check you Axis2 home here is the code I generated with the axis2 trunk. thanks, Amila. On Dec 3, 2007 4:49 PM, < [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: Hi Amila, As I said, I have the same issue (also tried it with the nightly build). You are right that the type and element name are the same. The problem is that I can't change the wsdl file. I just need to deal with this version. Strange in my opinion is that Axis 1.4 seems to generate more suitable code. Is there are different approach taken (from perspective of the complexType / element name issue)? Some clarification would be appreciated. Regards, Sietse ________________________________ From: Amila Suriarachchi [mailto: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> ] Sent: 03 December 2007 09:36 To: [email protected] Subject: Re: Strange generated java class names On Nov 23, 2007 11:41 AM, Simon Steinacker <[EMAIL PROTECTED]> wrote: Yes, I am using Axis2. This is the WSDL: http://pastebin.com/m1c167821 Please have a look at with a SNAPSHOT. here the problem is you have an element called findDocumentsResponse and a complexType called findDocumentsResponse so we have to rename one. But I changed this in trunk like this. if both element and complex type in same package the element name would have an suffix E. and if they are in different packages then have the original name. thanks, Amila. Thanks, Simon Amila Suriarachchi wrote: > Are you using Axis2? > Can you send your wsdl? > > thanks, > amila. > > On Nov 22, 2007 3:31 PM, Simon Steinacker > <[EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > wrote: > >> Hello, >> >> I have a wsdl and generate java classes out of it using the wsdl2java >> ant task. For example I have defined a response message named >> 'FindDocumentsResponse'. Axis2 generates the java class for that, but >> performs a renaming into something like 'FindDocumentsResponse11'. So it >> seems that it somehow appends a random number to the generated response. >> This only seems to be the case with service responses, since parameters >> are not affected by that phenomenon. >> Is there a way to circumnavigate this issue? Because it is rather >> inconvenient to use? >> >> Thanks for your help! >> Simon >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> >> > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -- Amila Suriarachchi, WSO2 Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Amila Suriarachchi, WSO2 Inc. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
