"Raj" <Raj@discussions.microsoft.com> wrote in message
news:53ADAB69-823A-4689-92A0-98007A0ED86C@microsoft.com...
> Hi Gaurabh,
> Thanks a lot for helping me out.
> Only thing i didn't get out of mail is last statement.
>
> You say "Infact, the recommended way is to be backward compatible. So,
> give
> the
> new method (method with new parameters) a new name -- in "operations"
> section."
>
> What do you mean my in "operations" section. can you pls explain in
> detail.
> I ping you a lot for this. Just last help for now.
> Thanks
> -rajesh
>
>
>
> "Gaurav Vaish (
www.EduJini.IN)" wrote:
>
>> Hi Raj,
>>
>> > Thanks for your reply first of all.
>>
>> Always welcome :-)
>>
>> > See I haven't removed any parameter instead I have added one. Min
>> > occurance
>> > is 1 for int and 0 for string param and both I have tried and found it
>> > working.
>>
>> What I meant was that for the new parameter is the minoccurs is 0
>> then
>> in that case the old proxy would not fail, because the parameter is
>> optional. The deserializer (SOAP Formatter) would give the paramter its
>> default value (null for reference types, 0 for numeric types etc)
>>
>> > Only concern is whether this is suggest approach, as you're saying no,
>> > which
>> > is why I think the existing set of web methods should not get
>> > disturbed.
>>
>> If you have made the new parameters with minoccurs=0 then no problems
>> as
>> far as usage is concerened. However since the proxy is not with the
>> latest
>> WSDL, it would not be recommended.
>>
>> Infact, the recommended way is to be backward compatible. So, give
>> the
>> new method (method with new parameters) a new name -- in "operations"
>> section.
>>
>>
>> --
>> Happy Hacking,
>> Gaurav Vaish
>>
http://www.mastergaurav.org >>
http://www.edujini.in >>
http://webservices.edujini.in >> -------------------
>>
>>
>>