You are viewing a plain text version of this content. The canonical link for it is here.

Posted to users@servicemix.apache.org by bolek1778 <ya...@yahoo.com> on 2007/07/24 17:32:38 UTC

Not enough message parts were received for the operation - 3.1.1 only

The code worked just fine on 3.1 After upgrading to 3.1.1 I'm getting an
error "Not enough message parts were received for the operation." What is
stranger is when I change the logging level to DEBUG it works just fine.
    <logger name="org.apache.servicemix">
        <!-- Works tith DEBUG, with INFO getting not enough message parts
error-->
         <level value="INFO"/> -
    </logger>

WSDL:
<?xml version="1.0" encoding="UTF-8"?><wsdl:definitions
name="nsrSyncRequest" targetNamespace="http://testnsr.com/sync"
xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:tns="http://testnsr.com/sync"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
    <wsdl:types>
    <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
targetNamespace="http://testnsr.com/sync">
	<xsd:element name="sendNSRSyncRequestResponse">
		<xsd:complexType>
			<xsd:sequence>
				<xsd:element name="errorCode" type="xsd:string"></xsd:element>
				<xsd:element name="errorString" type="xsd:string"></xsd:element>
				<xsd:element name="responseCode" type="xsd:string"></xsd:element>
				<xsd:element name="sourceOrderID" type="xsd:string"></xsd:element>
			</xsd:sequence>
		</xsd:complexType>
	</xsd:element>
	</xsd:schema></wsdl:types>
    <wsdl:message name="sendNSRSyncRequestRequest">
		<wsdl:part name="operationCode" type="xsd:string"></wsdl:part>
	    <wsdl:part name="sourceOrderID" type="xsd:string"></wsdl:part>
	</wsdl:message>
    <wsdl:message name="sendNSRSyncRequestResponse">
    	<wsdl:part name="parameters"
element="tns:sendNSRSyncRequestResponse"></wsdl:part>
    </wsdl:message>
    <wsdl:portType name="NSRSyncRequest">
    	<wsdl:operation name="sendNSRSyncRequest">
    		<wsdl:input message="tns:sendNSRSyncRequestRequest"></wsdl:input>
    		<wsdl:output message="tns:sendNSRSyncRequestResponse"></wsdl:output>
    	</wsdl:operation>
    </wsdl:portType>
    <wsdl:binding name="NewBinding" type="tns:NSRSyncRequest">
    	<soap:binding style="rpc"
    		transport="http://schemas.xmlsoap.org/soap/http" />
    	<wsdl:operation name="sendNSRSyncRequest">
    		<soap:operation
soapAction="http://testnsr.com/sync/sendNSRSyncRequest" />
    		<wsdl:input>
    			<soap:body use="encoded" namespace="http://testnsr.com/sync"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
    		</wsdl:input>
    		<wsdl:output>
    			<soap:body use="encoded" namespace="http://testnsr.com/sync"
encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
    		</wsdl:output>
    	</wsdl:operation>
    </wsdl:binding>
    <wsdl:service name="NSRSyncService">
    	<wsdl:port name="NewPort" binding="tns:NewBinding">
    		<soap:address location="http://www.example.org/"></soap:address>
    	</wsdl:port>
    </wsdl:service></wsdl:definitions>


Test SOAP message:
<?xml version="1.0" encoding="UTF-8" ?> 
<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<soapenv:Body>
<ns0:sendNSRSyncRequest xmlns:ns0="http://testnsr.com/sync"
soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
  <operationCode xsi:type="xsd:string">eee</operationCode> 
  <sourceOrderID xsi:type="xsd:string">eee</sourceOrderID> 
  </ns0:sendNSRSyncRequest>
  </soapenv:Body>
</soapenv:Envelope>
-- 
View this message in context: http://www.nabble.com/Not-enough-message-parts-were-received-for-the--operation---3.1.1-only-tf4136784s12049.html#a11765749
Sent from the ServiceMix - User mailing list archive at Nabble.com.

Re: Not enough message parts were received for the operation - 3.1.1 only

Posted by Gert Vanthienen <ge...@skynet.be>.

L.S.,

The easiest way to get this resolved, is probably by opening a JIRA and 
attaching a failing SA to that (or instructions for building one).  If 
this isn't an option, we need some additional information:
- Have you created a service in ServiceMix that corresponds with this 
WSDL or are you trying to invoke one externally that has this WSDL?
- If you have implemented it yourself: how is it implemented (jsr-181 or 
something else)?

Regards,

Gert

bolek1778 wrote:
> The code worked just fine on 3.1 After upgrading to 3.1.1 I'm getting an
> error "Not enough message parts were received for the operation." What is
> stranger is when I change the logging level to DEBUG it works just fine.
>     <logger name="org.apache.servicemix">
>         <!-- Works tith DEBUG, with INFO getting not enough message parts
> error-->
>          <level value="INFO"/> -
>     </logger>
>
> WSDL:
> <?xml version="1.0" encoding="UTF-8"?><wsdl:definitions
> name="nsrSyncRequest" targetNamespace="http://testnsr.com/sync"
> xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:tns="http://testnsr.com/sync"
> xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/">
>     <wsdl:types>
>     <xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> targetNamespace="http://testnsr.com/sync">
> 	<xsd:element name="sendNSRSyncRequestResponse">
> 		<xsd:complexType>
> 			<xsd:sequence>
> 				<xsd:element name="errorCode" type="xsd:string"></xsd:element>
> 				<xsd:element name="errorString" type="xsd:string"></xsd:element>
> 				<xsd:element name="responseCode" type="xsd:string"></xsd:element>
> 				<xsd:element name="sourceOrderID" type="xsd:string"></xsd:element>
> 			</xsd:sequence>
> 		</xsd:complexType>
> 	</xsd:element>
> 	</xsd:schema></wsdl:types>
>     <wsdl:message name="sendNSRSyncRequestRequest">
> 		<wsdl:part name="operationCode" type="xsd:string"></wsdl:part>
> 	    <wsdl:part name="sourceOrderID" type="xsd:string"></wsdl:part>
> 	</wsdl:message>
>     <wsdl:message name="sendNSRSyncRequestResponse">
>     	<wsdl:part name="parameters"
> element="tns:sendNSRSyncRequestResponse"></wsdl:part>
>     </wsdl:message>
>     <wsdl:portType name="NSRSyncRequest">
>     	<wsdl:operation name="sendNSRSyncRequest">
>     		<wsdl:input message="tns:sendNSRSyncRequestRequest"></wsdl:input>
>     		<wsdl:output message="tns:sendNSRSyncRequestResponse"></wsdl:output>
>     	</wsdl:operation>
>     </wsdl:portType>
>     <wsdl:binding name="NewBinding" type="tns:NSRSyncRequest">
>     	<soap:binding style="rpc"
>     		transport="http://schemas.xmlsoap.org/soap/http" />
>     	<wsdl:operation name="sendNSRSyncRequest">
>     		<soap:operation
> soapAction="http://testnsr.com/sync/sendNSRSyncRequest" />
>     		<wsdl:input>
>     			<soap:body use="encoded" namespace="http://testnsr.com/sync"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>     		</wsdl:input>
>     		<wsdl:output>
>     			<soap:body use="encoded" namespace="http://testnsr.com/sync"
> encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"/>
>     		</wsdl:output>
>     	</wsdl:operation>
>     </wsdl:binding>
>     <wsdl:service name="NSRSyncService">
>     	<wsdl:port name="NewPort" binding="tns:NewBinding">
>     		<soap:address location="http://www.example.org/"></soap:address>
>     	</wsdl:port>
>     </wsdl:service></wsdl:definitions>
>
>
> Test SOAP message:
> <?xml version="1.0" encoding="UTF-8" ?> 
> <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
> <soapenv:Body>
> <ns0:sendNSRSyncRequest xmlns:ns0="http://testnsr.com/sync"
> soapenv:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
>   <operationCode xsi:type="xsd:string">eee</operationCode> 
>   <sourceOrderID xsi:type="xsd:string">eee</sourceOrderID> 
>   </ns0:sendNSRSyncRequest>
>   </soapenv:Body>
> </soapenv:Envelope>
>