Sietse,

I had noticed the same happening for my skeleton class method parameters 
generated by Axis2. But that is not a problem for me since I anyway do not use 
the axis2 generated skeleton - I just use my own impl class and change the 
generated services.xml to refer to that.

Even if you use the axis2 skeleton, I would think that after you add the impl 
code in it, you would not let that be overwritten by an auto generated skeleton 
(except when you change webservice methods/signature, when you would need to 
add the changed methods into your impl class). So is this an issue?

There is also a somewhat connected issue about translation of operation names 
to method names that I have reported. See 
http://www.mail-archive.com/[email protected]/msg35508.html.


- Vish.

>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]
>Sent: Thursday, November 29, 2007 7:21 AM
>To: [email protected]
>Subject: RE: Strange generated java class names
>
>Hi Martin,
>
>The WSDL (including xsd's) can be found at:
>http://www.epcglobalinc.org/standards/epcis/epcis_1_0-schema-20070412.zi
>p
>
>I tried with the nightly build and also with axis2-1.3.
>
>Thanks in advance,
>Sietse
>
>-----Original Message-----
>From: Martin Gainty [mailto:[EMAIL PROTECTED]
>Sent: 29 November 2007 14:38
>To: [email protected]
>Subject: Re: Strange generated java class names
>
>Please post WSDL
>
>M-
>----- Original Message -----
>From: <[EMAIL PROTECTED]>
>To: <[email protected]>
>Sent: Thursday, November 29, 2007 8:07 AM
>Subject: RE: Strange generated java class names
>
>
>Hello everyone,
>
>I still didn't found a solution for this.
>
>Is there any update from Simon or Amila (or someone else) on this?
>
>Regards,
>Sietse
>
>-----Original Message-----
>From: [EMAIL PROTECTED]
>[mailto:[EMAIL PROTECTED]
>Sent: 23 November 2007 11:38
>To: [email protected]
>Subject: RE: Strange generated java class names
>
>Hi all,
>
>I have the same issue. It's kind of strange because, in my case, it is
>just a wrapper to the good class (i.e. HelloWorldRequest15 has only one
>field which is HelloWorldRequest). I tried to get rid of it using the
>-uw option but it doesn't help.
>
>The numbers are indeed random, every time I generate the sources I have
>other numbers. This pretty much ruins the automated build. Is there a
>workaround for this?
>
>Cheers,
>Sietse
>
>-----Original Message-----
>From: Simon Steinacker [mailto:[EMAIL PROTECTED]
>Sent: 23 November 2007 06:11
>To: [email protected]
>Subject: Re: Strange generated java class names
>
>Yes, I am using Axis2.
>This is the WSDL: http://pastebin.com/m1c167821
>
>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]> 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]
>
>
>---------------------------------------------------------------------
>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]
>
>
>
>---------------------------------------------------------------------
>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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to