question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

WSDL using element in part is not correctly imported

See original GitHub issue

Hi,

I created a SOAPUI project from a wsdl that define a message part with an element :

 <wsdl:message name="recupererSuiviParcoursCarteRequest">
   <wsdl:part name="recupererSuiviParcoursCarteRequestPart" element="metier:recupererSuiviParcoursCarteRequestElement"/>
 </wsdl:message>

Microcks is able to load my project but the SOAP operation is associated with the message name and not the element part. When I tried to send this request to the microcks serveur, there is a 404 (no operation found):

<soap:Body>
      <v2:recupererSuiviParcoursCarteRequestElement>
         ...

And when I changed the request (which is not valid against the wsdl) as follow, it works :

<soap:Body>
      <v2:recupererSuiviParcoursCarteRequest>
         ...

I do not have this issue on soapui running my mock.

I attached the project file.

Kind regards, Sébastien

VIES-soapui-project.zip

Issue Analytics

  • State:closed
  • Created 10 months ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
sfraigneaucommented, Nov 16, 2022

Hello Laurent,

My project has been imported with success on the nightly build. And now, my request with the message part element is working !

Congrats for your fix and thank you for your reactivity 👍

1reaction
lbroudouxcommented, Nov 10, 2022

Hi Sébastien,

Let me refresh my mind on WSDL + XSD + SOAP stuffs and I’ll see what’s possible to do. I’ll come back to you shortly.

Read more comments on GitHub >

github_iconTop Results From Across the Web

WSDL Not correctly imported in Visual Studio - Stack Overflow
I had to change several parts of the WSDL, including adding style="document" to each soap:operation, replacing part types with part elements ...
Read more >
Error "WSDL: The X element referenced by the Y part cannot ...
The Error "WSDL: The X element referenced by the Y part cannot be resolved" will show in the WSDL editor of IBM Rational...
Read more >
xs:choice not imported correctly from WSDL - MSDN
"XML Schema choice element allows only one of the elements contained in the <choice> declaration to be present within the containing element."
Read more >
K12972: WSDL files that do not contain a correctly ... - AskF5
WSDL files that do not contain a correctly defined targetNamespace may fail to load when you import them using the BIG-IP ASM Configuration ......
Read more >
Unable to import WSDL, if it contains import of ... - GitHub
I have checked Postman logfile renderer-requester.log and no error is logged during import. I have spotted, that if during WSDL import I click...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found