Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
Since
we checked the fix in on 2002-02-07, it would appear in today's (2002-02-08)
nightly build.
--
Tom
Jordahl
Macromedia
-Original Message-From: Thomas Börkel
[mailto:[EMAIL PROT
Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
HI!
I
tested the latest build from 2002-02-07 and there the problem is not
fixed.
Please
let me know how Russell want to deal with the appended "Service"
problem.
Regar
Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
Hi
Thomas!
I'm
going to let Russell deal with your first problem, but I think Tom and I
resolved the second one with our last fix. Can you check to see if the
current CVS works for you? T
Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
OK, I
found both problems I mentioned below by myself after a debug session (I don't
like this very much):
1.
"Service" is being appended to the name
Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
If I
change the Response definition of the current build, then .NET is
happy:
Normal
output from the current build:
Manuelly changed WSDL to:
Why is
this
Title: Changes in current build vs. alpha3 in WSDL generation: New problems with .NET 1.0
HI!
Why does the current build always append "Service" at the service name? Alpha3 did not do that and that was good.
Also, .NET issues an error now on the WSDL file:
Unable to impo
