I tried a wsdl with operation name = "class", "namespace" etc, and the .Net wsdl.exe generated C# code with method names="@class", "@namespace" etc. As these are valid identifier names in C#, this code did compile. By the way, I used the standard .Net framework SDK without the service pack.
I am no C# expert, but looks like this is a standard feature in C#, you can use keywords for identifiers by prefixing them with @. Shridhar > -----Original Message----- > From: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]] > Sent: Friday, April 05, 2002 10:31 AM > To: [EMAIL PROTECTED] > Subject: RE: dot Net > > > You are totally right. This is a bug that has not even been > addressed by > their latest release pack... What is funny (but not > surprising) is their > suggestion: "change your names"! Yeah right... Look like I > will have to > tell my customer to use Axis! > > Syvlain. > > -----Original Message----- > From: Glen Daniels [mailto:[EMAIL PROTECTED]] > Sent: Thursday, April 04, 2002 3:07 PM > To: '[EMAIL PROTECTED]' > Subject: RE: dot Net > > > > You mean a WSDL which specifies "param" as a parameter name > generates a C# > stub which won't build? > > If so, this sounds like a .NET bug (a surprising one at that > - are you using > the release version?). Axis deals with mangling java keyword > identifiers, > and other systems should do the same for their particular > environments.... > > --Glen > > > -----Original Message----- > > From: St-Germain, Sylvain [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, April 04, 2002 2:51 PM > > To: Axis Dev (E-mail) > > Subject: dot Net > > > > > > I though you guys might appreciate to know that dotNet > > does not allow to use "class" and "namespace" (in VB) and > > param (in C#). > > The generated code does not build! > > > > Has anyone yet built a WSDL with all the common languages > > reserved keywords? > > That would be a good test. > > > > Sylvain. > > > > This message may contain privileged and/or confidential > > information. If you > > have received this e-mail in error or are not the intended > > recipient, you > > may not use, copy, disseminate or distribute it; do not open any > > attachments, delete it immediately from your system and > > notify the sender > > promptly by e-mail that you have done so. Thank you. > > > > This message may contain privileged and/or confidential > information. If you > have received this e-mail in error or are not the intended > recipient, you > may not use, copy, disseminate or distribute it; do not open any > attachments, delete it immediately from your system and > notify the sender > promptly by e-mail that you have done so. Thank you. >
