Hello Amila, hello everybody first of all thank you for your answer.
> > I got a question regarding the naming of parameters and exceptions > > in the generated stub code for the client. Why are numbers added to the > > parameter > > names? > this is a technique done to avoid any possible compilation issues. And there is no way to disable this? I chose my parameter and method names carefully to ease things for the developers using my webservice. I do not see how compilation issues could arise from parameter names. > > I still do not have found out why sometimes the word "Exception" is > added to custom Exception classes and sometimes it is not?? If I have an > > Exception-class called MyException in the service implementation I sometimes > > find an inner class in the service stub which is called MyExceptionException > > instead of MyException > if there is an wsd:fault message for an operation it generates an exception > class for that which has the sufix 'Exception'. But if you have a schema > element with the name MyException it generates an ADB class for that and > does not add a sufix. I am still new to Axis/Axis2. I created an interface and afterwards an implementation of this interface. Then I used the Eclipse's Webservice wizard selecting the Bottom-Up-Method pointing the wizard to my implementation. Finally I used the Service Archiver to export my webservice. My service implementation includes exception classes I created and since they are Exceptions they are all named in this way: MyFirstCustomException, MySecondException. Is it necessary to create a schema to avoid this behaviour? If yes, how do I start? Best regards and thank you for your help, Sebastian
