Hi Christian, I would also go the same way of the solution. I am a German as well and we had the same thing to do with one of our services. I just changed the existing service by renaming the classes and methods and every language specific part.
And in the future, I would try to produce always english services unless the customer explicitly states that he wants to have that service in German. The result of the called methods (e.g. a message) could, of course, still be in German. HTH, Matthias. > -----Ursprüngliche Nachricht----- > Von: Christian Lipp [mailto:[EMAIL PROTECTED] > Gesendet: Freitag, 6. Juni 2008 13:56 > An: axis-user@ws.apache.org > Betreff: service language > > Hello! > > We are using Axis V1.x and have some services implemented in German > language. > Now we have a new project in a foreign country, so we are forced to > translate our interfaces to the English language. > > In my understanding I have to > - change the interface to English > - generate classes (also with English names and attributes) > - refactor the application from the usage of the german classes to the > usage > of the english classes > > Is the solution the same when using Axis V2.x? > Or is there a possibility to map two interfaces with the same structure > but > with different languages to the same class? > If yes, how is this done? > > Thanks for your help in advance, > CL > > > --------------------------------------------------------------------- > 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]
