Thank you for exposing the solution, guys.
I work with Tatto and I have made the modifications on the file and we
were able to generate the proxy.
Do you have an estimated date for the next release?
Regards,
Silvano
On Nov 19, 2007 8:14 AM, Matthew Peters <[EMAIL PROTECTED]> wrote:
>
> Rob is e
Rob is exactly right.
If you change two lines in SCA/Bindings/soap/
ServiceDescriptionGenerator.php to add the namespace prefix "wsdl" to
the generated wsdl, it will validate. Sorry about that.
I have checked in a change which will be in the next release.
Line 196 should read
$types
Hi Caroline,
Caroline Maynard wrote:
> It's sad but true that different programs don't have the same criteria
> for deciding what is valid WSDL. If you look back in the mailing list or
> in our bugs list, you'll see there have been a couple of issues about
> the .NET tools being quite picky comp
On Tue, 2007-11-13 at 10:50 -0200, Tatto de Castro wrote:
> Paul Scott, the problem happens with your wsdl too (error message
> follows below).
>
If I am not mistaken, the nameSpace is (one) of the problems there. I
need to fully qualify that at least before you try again. Thanks Tatto,
app
On Tue, 2007-11-13 at 10:23 +, Caroline Maynard wrote:
> Alive, just sleeping ...
>
Sleep, whats that? Coffee ;)
> It's sad but true that different programs don't have the same criteria
> for deciding what is valid WSDL. If you look back in the mailing list or
> in our bugs list, you
Paul Scott wrote:
> On Mon, 2007-11-12 at 15:16 -0200, Tatto de Castro wrote:
>> I'm having a strange problem when I try to use the Web Services
>> Description Language Tool (Wsdl.exe) from .NET Framework Tools. I'm
>> getting an error when I try to use the wsdl.exe to create the C#
>> client
On Mon, 2007-11-12 at 15:16 -0200, Tatto de Castro wrote:
> I'm having a strange problem when I try to use the Web Services
> Description Language Tool (Wsdl.exe) from .NET Framework Tools. I'm
> getting an error when I try to use the wsdl.exe to create the C#
> client proxy class based on the
