Hi james .. sure you can ...you can check input in the serivice and send error..
But with overloaded method you are adding another conceran to ur lap .. The webservices (To me at least ) is not take a class (java or C) and publish it. you do not want everything. To me overloaded method is something that can be droped. It add unnecsarry overhead to the engine by supporting it. (I feel so). Thanks for your tike Srinath -- Simplicty is the ultimate requirement of all time, yet there is nothing like complexity fascinates the humanbeings ... On Wed, 20 Aug 2003 12:21:05 -0400, James Black wrote > [EMAIL PROTECTED] wrote: > > >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 :) > > > If you have good unit tests, then you can ensure that your > overloaded methods can properly handle incorrect inputs, if nothing > else, by sending an error message to that effect. > > -- > "We do not lose our identity in our relations with others; in part, > at least, we achieve our identity by those relations." Tony Blair, 1993 -- Lanka Software Foundation (http://www.opensource.lk) Promoting Open-Source Development in Sri Lanka
