removed xsi: before minOccurs

[Bjorn-Nilsson]

a nice pull request if you think this is a good idea! :)

[inossidabile]

The problem is that Java won't work with this. This is not valid XML due to namespaces collapse. Are you sure .NET works with this? Cause it's quite strange to me.

You can also try to set xsd: namespace. Will it work then?

[Bjorn-Nilsson]

This is second hand information for me so no, I'm not sure. I don't use .NET myself. I can ask if it works with xsd: But isn't it strange that so many use invalid XML? I'm new to SOAP so I just try to figure it out.

[inossidabile]

It may not be invalid. Everything depends on how you define your schemas and namespaces. minOccurs is defined inside of XMLSchema declaration. With 'xmlns:xsd' => 'http://www.w3.org/2001/XMLSchema' I bind XMLSchema to xsd namespace. And therefore it should be accessible from within. You should ask if it works with xsd or we have to find another way out. Since we can't break Java in favor of .NET. We have to support both :)

[Bjorn-Nilsson]

I spoke to my .NET colleague, apparently it doesn't work for them to have minOccurence in any sort of namespace so at least for now I will have to use my own fork. Thanks for the info! :)

[inossidabile]

.NET compatibility is very important. I'll try to investigate if we can force Java to use it without namespaces too.

[inossidabile]

And lol I succeeded. Try the master pls.

[inossidabile]

And now it stopped working with PHP. I hate SOAP 😱. However you should try to check .NET against master anyway. I think I'll be able to do something with PHP too.

[Bjorn-Nilsson]

Haha, I know what you mean.. Time for lunch now but I will try as soon as I get back!

[inossidabile]

Okay. I've reformed WSDL to be a valid XML. Since types section is in XML Schema namespace we can omit the 'xsd' namespace indeed. However the problem appeared to be in message -> part section. It can not be omitted there since part is a tag from WSDL namespace. Therefore it's still there.

You should check if it makes .NET happy. If it's not... the only thing that can break .NET client is the array as a direct parameter. As long as you wrap all your direct arrays into something it is supposed to be happy.

So instead

:args => [:integer]

you should use

:arge => {:zomg_numbers => [:integer]}

And it should work with master. Could you please approve that?

[Bjorn-Nilsson]

According to my colleague it works now (with current master), great! Thanks for your insanely quick responses! :)

[inossidabile]

✊😍✊