Invalid Body Entry error from pub.client:soapHTTP

Dear Friends
It is my pleasure to be with u now, as it is my first time to send anythread here.

I face an Issue which is:

I’m creating a Web Service which Invokes within it a Flow Service
The Flow Service is Working correctly.

I added before and after it the needed Built In functions that makes it a Web Service that deals with SOAP Message.

The Input / Output are document Types with Namespaces ,

The WSDL is Created with No Errors.
The Web Connector is Done smoothly.

But while Testing the Web Service, It works v.well, Until it reaches the Built in Function → pub.client:soapHTTP
It shows me error → [ISS.0088.9142] Invalid Body Entry. SOAP Body Entries must have a namespace name.

What makes me confised is that i feel that the SOAP Messae is follwoing the Standards in the Documentation !!! ???

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/"
xmlns:SOAP-ENC="
http://schemas.xmlsoap.org/soap/encoding/"
xmlns:xsd="
http://www.w3.org/1999/XMLSchema"
xmlns:xsi="
http://www.w3.org/1999/XMLSchema-instance"
SOAP-ENV:encodingStyle="
http://schemas.xmlsoap.org/soap/encoding/">
SOAP-ENV:Body
<GSO:GenerateSO xmlns:GSO="
http://www.MeMega.com/SalesOrder_SOAP/">
4244

222
2


221
3

</GSO:GenerateSO></SOAP-ENV:Body>
</SOAP-ENV:Envelope>

Please Help me ,

Using IS 6.5 SP2 with WebSvcsXML_Fix2, I whipped up a 2-line test service that used pub.soap.utils:stringToSoapData to convert your sample soap doc to a soapdata object and then used pub.client:soapHTTP to post it to my local server. No error messages were thrown.

What version of IS are you using? Are you sure the error is coming from the pub.client:soapHTTP call?

Mark

Thanks for ur reply …
I’m using version 6.1 with No Updates …

By Now i ve a Different Error when i reach the pub.client:soapHTTP

<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" xmlns:xsd="http://www.w3.org/1999/XMLSchema">
SOAP-ENV:Body
SOAP-ENV:Fault
SOAP-ENV:Client
[ISS.0088.9134] Exception occurred while processing the body of the message
http://localhost:5555/soap/default
<detail xmlns:webM="
http://www.webMethods.com/2001/10/soap/encoding">
webM:exception
webM:classNamecom.wm.pkg.art.error.DetailedServiceException</webM:className>
<webM:message xml:lang="">[ART.117.4002] Adapter Runtime (Adapter Service): Unable to invoke adapter service SalesOrderSOAP.Adapters.BusinessFunctions:F4211FSBeginDoc.

BSFN error code: 2
Number of error: 2
Error item 1
ErrorLevel : 1
ErrorID : 103
DDItem : 041H
lineNumber : 720
fileName : b4200310.c
subText :
alphaDescription : Error: Sold to address number is invalid
glossaryText : CAUSE . . . . The number in the sold to field is not found in the address book.

RESOLUTION. . Enter a valid sold to address number on the ticket.

even i enter the Ship To Address Number a Valid Value in my SOAP Message:
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="
http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/1999/XMLSchema" xmlns:xsi="http://www.w3.org/1999/XMLSchema-instance" SOAP-ENV:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
SOAP-ENV:Body
<wsdns1:GenerateSO xmlns:wsdns1="
www.memega.com">
4244

222
1


221
2

</wsdns1:GenerateSO></SOAP-ENV:Body>
</SOAP-ENV:Envelope>

please need ur help … thx

Those errors are specific to your application. Apparently, your invoke of SalesOrderSOAP.Adapters.BusinessFunctions:F4211FSBeginDoc is not providing the correct data. If you believe that the correct data is in your soap request, then the issue most likely lies with how you are extracting the data from the soap body and using it to invoke the adapter service.

Build a simple test harness that uses pub.soap.utils:stringToSoapData to build the soap request that believe you are sending and then sends this soap request (soapRequestData object) to your wrapper service which is extracting data from the body and invoking your adapter service.

You can use the “step into” feature to see what is happenging in your wrapper service.

Mark

Dear
As the Specific Services Invoked Standalone without wrapping it to be a Web Service, It works great … with the same input data equivalent to what is included in the SOAP Message …
so could u help me know the steps and tricks needed to convert a service to be a Web Service (SOAP - Message) …
even i follwoed the WebMethods documentation steps …
Thanks alot

Did. That. Already.