By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
443,333 Members | 1,070 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 443,333 IT Pros & Developers. It's quick & easy.

SOAP 2K3 and 2K5 (Beta 2) BIG Change?

P: n/a
In 2k3 code generated from certain WSDL files all is valid, but in 2k5 it
isn't. The difference appears to be that wrapped parameter names no longer
appending a 1 to themselves to avoid name conflicts. Is this true and if
so, is there a way to revert back to 2k3 compatibility as I have hundreds of
lines of code that are going to stop working if we deploy 2k5 when it roles
out this way!

Thanks!
Derek

--
Derek Martin
593074
Nov 21 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
BTW, if this is of any help, the WSDL file is clean (validates) and is built
on a Linux machine, so we might have a platform issue here?
Derek

"Derek Martin" <dm*****@DONTSPAMMEokstateDOT.edu> wrote in message
news:uv**************@tk2msftngp13.phx.gbl...
In 2k3 code generated from certain WSDL files all is valid, but in 2k5 it
isn't. The difference appears to be that wrapped parameter names no longer
appending a 1 to themselves to avoid name conflicts. Is this true and if
so, is there a way to revert back to 2k3 compatibility as I have hundreds
of lines of code that are going to stop working if we deploy 2k5 when it
roles out this way!

Thanks!
Derek

--
Derek Martin
593074

Nov 21 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.