Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SOAP messages naming issue #119

Open
tkrypton opened this issue Feb 23, 2018 · 2 comments
Open

SOAP messages naming issue #119

tkrypton opened this issue Feb 23, 2018 · 2 comments

Comments

@tkrypton
Copy link

tkrypton commented Feb 23, 2018

I have a strange interoperability problem where KDSoap uses different response names as the partner.
It seems to boil down to WSDL definitions like:

<operation name='Foo'>
   <input name='FooRequest' message='FooInput'/>
   <output name='FooResponse' message='FooOutput'/>
</operation>

<message name='FooInput'>
</message>

<message name='FooOutput'>
  <part name='return' type='xsd:int'/>
</message>

KDSoap generates responses like:
... <soap:Body> <FooOutput> <return>0</return> </FooOutput> </soap:Body> ...

Where my communication partner expects:
... <soap:Body> <FooResponse> <return>0</return> </FooResponse> </soap:Body> ..

From my understanding KDSoap is right, but where do I find references in the standard RFCs
to prove this?

[edit: probably nowhere, because these definitions have contradicting names?]

Thanks for any help,
Uli

@tkrypton
Copy link
Author

I just see that my expamples got severly mangled during post. Will try to fix the post...

@tkrypton
Copy link
Author

Now the vital XML should be readable. If not, please yell at me.

@tkrypton tkrypton reopened this Feb 26, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant