Document Style webservice : Operation Identification problem..

I've a problem with webservice, I use document-literal-unwrapped style webservice and I've cnlosed my WSDL and SOAPEnvelope herewith.

Here's a snippet of my Soap Message..

--

<soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/">

<soap:Body >

<rsq:RSDocument xmlns:rsq="urn:abc:abc-query:xsd:1"

xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

schemaVersion="1.0" creationDate="2006-07-06T00:00:00.000Z">

<RSHeader>

<rsq:StandardBusinessDocumentHeader>

.

.

.

.

.

</rsq:StandardBusinessDocumentHeader>

</RSHeader>

<RSBody>

<rsq:Activate>

<queryName>SimpleQuery</queryName>

<params>

.

.

--

My problem is the tag which is immedietly below the SOAP:BODY is being taken to recognize as the name of operation.

Here, Actually, the <rsq:Activate> will be the Tag to identify the operation but, it assumes RSQueryDocument (which is the immediete next node to <SOAP:BODY>) as its operation and it complains the following error.

<faultstring>

caught exception while handling request: unexpected element name:

expected="urn:abc:abc-query:xsd:1"Activate,

actual="urn:abc:abc-query:xsd:1"RSQueryDocument

</faultstring>

Is it possible to keep the Tag (which corresponds to an Operation) not immedietly below <soap:body>..? Or should that be immedietly below <soap:body>..?

Can you please help me in this regard..?

Thanks

Rajasekaran

[1660 byte] By [Rajasekaran_sun_forum_screena] at [2007-11-27 4:48:05]
# 1

The element name of the element immediately following the <soap:body> should be exactly the same name as the element name specified by the wsdl:input message body part. For example, if the following was my input message:

<wsdl:message name="echoDataIn">

<wsdl:part name="data" element="types:data"/>

</wsdl:message>

Then the env would be

...

<soap:body>

<types:data>...</types:data>

</soap:body>

..

dkohlerta at 2007-7-12 10:00:54 > top of Java-index,Enterprise & Remote Computing,Enterprise Technologies...