Hi Jim ,Jeff yap i am quite agree that it better to keep away from overloaded methods ...
I have wirte overloaded methods and send them wrong requests ... e.g. send three parameters to method expect two vise-versa .. Some time they work ... (when they shuld fail..) depend on the service.. If u r going 2 meke a real serious application better to keep away .. you can give a other name :) Srinath On Tue, 19 Aug 2003 15:04:07 -0700, Jeff Greif wrote > Also, overloaded methods are an area where either the server or > client software are liable to do a bad job. It's my impression that > if you're operating in a tightly controlled environment where you > can test the client varieties and server code (and not expect random > users to be invoking your service using a whole raft of different > client platforms), you might be able to make it work, especially if > you have the flexibility to change platforms if it doesn't. > Otherwise you're probably inviting trouble. It's strange, because > the overload resolution does not seem that difficult; I guess it's > just a small part of a pretty substantial hunk of software and > likely to fall through the cracks. > > Jeff > ----- Original Message ----- > From: "Jim Murphy" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Tuesday, August 19, 2003 12:01 PM > Subject: Re: Can methods in a service be overloaded > > > You can do that but the WSDL generated will not conform to the WS-I > > Basic Profile[1], specifically R2304. > > > > Regards > > Jim Murphy > > Mindreef, Inc. > > > > > > [1] http://www.ws-i.org/ > > > > > > Guofeng Zhang wrote: > > > > > the service I published has the following operations: > > > void beat() ; > > > void beat( long b ) ; > > > are they correct? > > > > > > > > > > > > -- Lanka Software Foundation (http://www.opensource.lk) Promoting Open-Source Development in Sri Lanka
