Forum Discussion

rockjj's avatar
rockjj
16 years ago

WSDL/XSD Changes not refelecting in SOAPUI bug

I created a web services based SOA composite using Oracle SOA 11g. WSDL generated using an XSD. Did some testing in SOAPUI for the old composite, worked well. I then did some refactoring of the XSD in Oracle SOA 11g. However, the SOAPUI keeps referencing the same old XSD namespace. eg: old code xmlns:cad="http://test/org/Cadmsg" instead of new namespace is xmlns:ns1="http://test/org/Cadmsg". The request message generated using SOAPUI keeps inserting cad as the namespace prefix. Where in the background does soap envelope code gets generated in a SOAPUI. Is the old XSD/WSDL cached somewhere. I even tried uninstalling and installing SOAPUI again. Please suggest

It comes up like this

soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header></soap:Header>
<soap:Body xmlns:cad="http://test/org/Cadmsg">
<cad:odsCadDataSet>
<cad:odsCadCase>


instead of

soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">
<soap:Header></soap:Header>
<soap:Body xmlns:ns1="http://test/org/Cadmsg">
<ns1:odsCadDataSet>
<ns1:odsCadCase>


The same sample message in the Oracle provided console comes properly as ns1 for namespace prefix.
Thanks

1 Reply

  • SmartBear_Suppo's avatar
    SmartBear_Suppo
    Icon for Alumni rankAlumni
    16 years ago
    Hi!

    The actual prefix used ("ns1" or "cad") has no significance, it could be called "alsdjaskjskdjs" from a technical point of view. The actual namespace is the same in both messages ("http://test/org/Cadmsg") so the messages are the same and should be handled equally. If your server or webservice is requiring use of a specific namespace prefix then that is a bug in itself and needs to be fixed accordingly.

    regards!

    /Ole
    eviware.com