Watch, Follow, &
Connect with Us

QualityCentral

Public Report
Report From: Delphi-BCB/SOAP/WSDL Importer    [ Add a report in this area ]  
Report #:  33205   Status: Closed
Wrong tag in SOAP message
Project:  Delphi Build #:  7&2006
Version:    10.0 Submitted By:   Registered User
Report Type:  Basic functionality failure Date Reported:  8/29/2006 6:31:45 AM
Severity:    Commonly encountered problem Last Updated: 3/20/2012 2:24:39 AM
Platform:    All platforms Internal Tracking #:   241795
Resolution: Fixed (Resolution Comments) Resolved in Build: :
Duplicate of:  None
Voting and Rating
Overall Rating: (3 Total Ratings)
5.00 out of 5
Total Votes: 7
Description
When Delphi generates the soap message, the element following <body> is taken from "operation name" in the wsdl-file:

<soap:envelope>
    <soap:body>
        <myMethod>
            <x>5</x>
            <y>5.0</y>
        </myMethod>
    </soap:body>
</soap:envelope>

In the above example "operation name" is myMethod in the wsdl-file.

Other tools (like Altova XML Spy) picks "myMethod" from here (wsdl file):

<types>
    <schema>
        <element name="myMethod">

If "element name" and "operation name" differs in the wsdl file, the Delphi SOAP message is wrong.

lso Delphi shoud pick "myMethod" from "element name" in the wsdl-file.

Example picked from:

http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/

Listing 8 and 9.
Steps to Reproduce:
Modify a OK wsdl-file where "element name" and "operation name" have the same value. Change "operation name". Import this wsdl-file and test.
Workarounds
Modifiy the wsdl-file (change 2 ea. "operation name" so that it equals "element name").
Attachment
None
Comments

Registered User at 9/4/2006 10:33:50 AM -
To clarify: When document style is used, the input variables should be wraped by the name of the input record (not the operation name as for RPC style).

http://www-128.ibm.com/developerworks/webservices/library/ws-soa-intersoap/index.html

http://www-128.ibm.com/developerworks/webservices/library/ws-whichwsdl/

Bart van der Werf at 11/15/2006 3:38:46 AM -
this bug prevents clients to interop with out code, error messages reported because of this include:



org.apache.axis2.wsdl.codegen.CodeGenerationException: Error parsing WSDL
Caused by: WSDLException (at /definitions/binding/operation/input): faultCode=INVALID_WSDL: Element '{http://schemas.xmlsoap.org/wsdl/}input' contained unexpected attributes: 'message':

CANAL TP Directeur Technique at 1/16/2007 3:48:16 AM -
Another example with the same problem:
http://qc.borland.com/wc/qcmain.aspx?d=38169

Server Response from: ETNACODE01

Copyright© 1994 - 2013 Embarcadero Technologies, Inc. All rights reserved.