Dear list.
Thanks to Amila for solving the issue so fast :-) It's much better working now
without those numbers!
Thanks a lot.
Stefan.
-------- Original Message --------
Subject: Re: Axis2 exception code generation
Date: Mon, 30 Jun 2008 11:35:38 +0530
From: Amila Suriarachchi <[EMAIL PROTECTED]>
To: Stefan E. Funk <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
<[EMAIL PROTECTED]>
fixed the issue. Please have a look at with a nightly build.
Please send these mails to Axis2 user list. where a lot of people can
benifit from it.
thanks,
Amila.
On Thu, Jun 26, 2008 at 2:35 PM, Stefan E. Funk <[EMAIL PROTECTED]>
wrote:
Hi Amila.
Thanks for replying. Please find my WSDL file as an attachment. I don't
think there are databinding classes with the same name (or I just did not
find them...)
Thanks for looking into it.
Stefan.
Amila Suriarachchi wrote:
On Wed, Jun 25, 2008 at 5:13 PM, Stefan E. Funk <[EMAIL PROTECTED]>
wrote:
Hello all.
Sorry for this maybe dull question, but I didn't find anything on that
topic
anywhere:
I would like to know, why the WSDL2Java code generator generates
exceptions
from the WSDL and adds a continous number to all exception class names,
e.g.
MyOwnException0, SecondException1, ExceptionXyz2, etc.
Can that numbers be avoided at code generation time somehow? The numbers
itself would be no peoblem, if they *wouldn't change* every time we
change
something in our WSDL file. So all exception names must be changed in all
server and client classes, too.
Maybe someone can tell me, how we can get rid of them :-)
Here the problem is that there may be a Databinding class with the same
name. If you could send a wsdl I can verify. One option is to use -p
option
and point generated service classes to different package.
thanks,
Amila.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
