Overloaded operations are permitted in SOAP 1.1, but they've been outlawed in SOAP 1.2. And even in SOAP 1.1, the spec doesn't explain how to make overloaded operations work, therefore they often don't. And it definitely causes interop problems.
SOAP uses a much simpler mechanism than Java to identify the signature of a message. In SOAP, the signature is defined only by the QName of the child element of the <soap:Body> element. Hence SOAP cannot distinguish between two signatures that have the same method name. Anne On 8/2/05, Yakulis, Ross (Ross) <[EMAIL PROTECTED]> wrote: > > > I searched on this and saw one post from Anne Thomas Manes that basically > said, > avoid using overloading of operations. > > Could Anne or anyone else explain why? > > Thank you, > > Ross
