wscompile wsi flag

[Kevin G Scott]

Hello,
I was playing a little with the wscompile tool that comes with the JWSDP 1.5 and working on generating a client for a WSDL. When I specify the f:wsi option, all my message signatures seem to pick up the wrapped element names as types, so that I get operations like MethodNameResponse methodName(MethodNameRequest). When I leave this flag off I get the correct signature. I don't why this happens and the only thing in the document for this flag is that it "enable(s) WSI-Basic Profile features." Can anyone explain this observed behavior?

Thanks in advance!

[Jim Baiter]

The Basic Profile specification guarantees that your web service will be interoperable across platforms (e.g. Microsoft, Java, etc.). The flag will generate wrappers so your messages will comply.

[Kevin G Scott]

So does that mean that the wrapped paradigm isn't fully interoperable?